m length of identifiers:64
Maximum columns in an index: 32
Date/time type storage: floating-point numbers
Maximum length of locale name:128
LC_COLLATE: C
LC_CTYPE: C
-Original Message-
From: Feng Ch
counter when it happens again.
Thanks!
-Original Message-
From: Tom Lane [mailto:[EMAIL PROTECTED]
Sent: Friday, August 24, 2007 12:11 PM
To: Stefan Kaltenbrunner
Cc: Feng Chen; Alvaro Herrera; Gregory Stark; Marc Schablewski;
Decibel!; pgsql-bugs@postgresql.org
Subject: [SPAM] Re: [SPAM]
Thanks for the replies! I guess it's time for 8.1.9 then. Will keep you
informed afterwards!
-Original Message-
From: Andrew Sullivan [mailto:[EMAIL PROTECTED]
Sent: Friday, August 24, 2007 10:14 AM
To: Andrew Sullivan
Cc: Feng Chen; Alvaro Herrera; Gregory Stark; Marc Schabl
VERSION = PostgreSQL 8.1.2
-Original Message-
From: Alvaro Herrera [mailto:[EMAIL PROTECTED]
Sent: Friday, August 24, 2007 10:02 AM
To: Feng Chen
Cc: Gregory Stark; Marc Schablewski; Decibel!; pgsql-bugs@postgresql.org
Subject: [SPAM] Re: [BUGS] BUG #3484: Missing pg_clog file / corrupt
We also have the same exact problem - every 5 to 10 days when the data
get to some size, PostgreSQL complains about missing pg_clog files, and
invalid page headers during either vacuum or reindex operations.
The problem happens on different customer sites with Linux 2.6.11.
There is one particula
me-archive.gz contains data up to Data-0. However, the
truncated database does not have Data-1, Data-2, and Data-3 in it!
Why is that? I thought truncate supports transaction now - we use
PostgreSQL 8.1.2.
Thank you!
Feng
-Original Message-
From: Tom Lane [mailto:[EMAIL PROTECTED]
S
Hello there,
I was trying to do a live db archive using the following steps:
1. Open a connection to the database;
2. With the connection, do the following:
BEGIN;
SET transaction ISOLATION level SERIALIZABLE;
3. Execute the following from the Linux shell:
pg_dump dbname
Hello,
I'm wondering if anyone has experienced the same problem and is it fixed
in the new Postgres release (We use Posgtgres 8.1.2, psqlodbc.so 7.2.5
(moving to 8.2.200), unixODBC 2.2.11 (moving to 2.2.12), running on
Linux OS.):
We have a recurring problem that the return type (a customer def
Hello,
I'm wondering if anyone has experienced the same problem and is it fixed
in the new Postgres release (We use Posgtgres 8.1.2, psqlodbc.so 7.2.5
(moving to 8.2.200), unixODBC 2.2.11 (moving to 2.2.12), running on
Linux OS:
We have a recurring problem that the return type (a customer defin
