Description:
General Discussions about PostgreSQL
|
|
|
Will there be an official pg_migrator release?
|
| |
Hi, the project page of pg_migrator still shows it as a release candidate. Will there be an official release of it, now that 8.4 is out of the door? Including Windows binaries? Regards Thomas
|
|
Documentation - PgAdmin
|
| |
Hi, Congratulations on the release of version 8.4. I am surprised that pgAdmin's help link is now directed to the documentation website of postgresql. The embedded help CHM was not packaged with it. This implies that anytime one needs help on a simple syntax, one must connect to the internet. Was this by design or omission?... more »
|
|
Function Issue and casting
|
| |
Hi friends, It's my first time I'm writing to the list. All days I enjoy the list! I declare a function, and when I want to call this, it fails. My function: CREATE OR REPLACE FUNCTION alta_docente(integer,varchar,v archar,varchar,bigint,varchar, integer) RETURNS VOID AS $body$ declare codigo integer;... more »
|
|
Pls help
|
| |
2009/7/4 Roseller A. Romanos <don2_...@yahoo.com>: ...you cannot copy postgres data files from one computer to second. PostgreSQL is not MySQL. Use pg_dump instead or copy statement. 1. on PC1 pg_dump -t yourtable yourdatabase > yourtable.sql 2. copy yourtable.sql file from PC1 to PC2 3. on PC2 psql yourdatabase < yourtable.sql... more »
|
|
Store derived data or use view?
|
| |
I have a table which stores the absolute longitude of a planetary position, eg: MERCURY --------------- 157.65 SATURN ------------- 247.65 When 2 planets are a certain distance apart there is an 'aspect', eg. 90 degrees is a "square" aspect I wish to record these aspects for different user profiles and eventually do searches for users who have the same aspect(s). Would it be better, in terms of search speed/efficiency, to calculate and store the aspect data, eg. Mercury/Saturn square, or should I just store the longitude data and create a view with the calculated aspects? I anticipate a large dataset of users so search speed/efficiency is very important.... more »
|
|
REINDEX "is not a btree"
|
| |
Hello! I got into a situation I don't know how the get out .. First, I could not access to my biggest database in postgre anymore because it suddenly gave the error (after long time working with no problems) ...After trying with several backups with no success, I did a vacuum and I tried to REINDEX the database (in the standalone back-end).... more »
|
|
|