Ray Madigan wrote:
> I think I just made a huge error. I just upgraded all of my systems and in
> the process I just upgraded the data base from 8.1 to 8.3. At least I think
> it was 8.1. Anyway the postmaster won't run and I can't backup the old
> database without a hue effort. Is there a way
I think I just made a huge error. I just upgraded all of my systems and in
the process I just upgraded the data base from 8.1 to 8.3. At least I think
it was 8.1. Anyway the postmaster won't run and I can't backup the old
database without a hue effort. Is there a way around this or do I have to
Hi All,
The following is the message we had got while setting up postgres
database. This message was overlooked when we setup but now we have
found the discrepancies. For now the database are created with encode
type as UTF8 but the locale settings are ISO8859-1 in postgresql.conf.
The question i
Greetings,
I'm trying to configure Postgres on a test box to I can the upgrade
my production box. I am getting an error as follow:
configure:17671: checking test program
configure:17686: gcc -o conftest -O2 -Wall -Wmissing-prototypes -
Wpointer-arith -Winline -Wdeclaration-after-statement -
"Daniel Cristian Cruz" <[EMAIL PROTECTED]> writes:
> I had a problem today, where pg_dump was locking a concurrent DROP TABLE,
> and it was another table, not the table in the COPY running. Is it normal?
Yes. pg_dump acquires ACCESS SHARE lock on all the tables it's
intending to dump. Without th
Helllo,
I had a huge database with a dump backup routine.
I had a problem today, where pg_dump was locking a concurrent DROP TABLE,
and it was another table, not the table in the COPY running. Is it normal?
Some kind of bug or is it expected?
I'm using 8.2.4 (I need to rewrite dblink functions b
