The following bug has been logged online:
Bug reference: 2865
Logged by: Leo
Email address: [EMAIL PROTECTED]
PostgreSQL version: 8.2
Operating system: Windows 2003
Description:Cannot save the data in pgAdmin
Details:
If there is only one record in a table, if I
The following bug has been logged online:
Bug reference: 5617
Logged by: Leo Shklovskii
Email address: l...@thermopylae.net
PostgreSQL version: 8.4.4
Operating system: Windows 7 (x86)
Description:pg_restore behaves unexpectedly on 'invalid' command
line
Det
hello:
i see a lot ,"missing chunk number 0 for toast value 96635 in
pg_toast_2619",," in background aler log.select * from iclock ,no data
retrun,indicate missing chunk number 0 for toast value 96635 in
pg_toast_2619.
i use pg_dump table,then truncate table,then pg_dump it current
data
pg version is 9.1.2
--
View this message in context:
http://postgresql.1045698.n5.nabble.com/select-table-indicate-missing-chunk-number-0-for-toast-value-96635-in-pg-toast-2619-tp5682176p5682273.html
Sent from the PostgreSQL - bugs mailing list archive at Nabble.com.
--
Sent via pgsql-bugs mail
hello:
i execute any operation in hot standby database,it indicates that index
pg_class_relname_nsp_index contains unexpected zero page at block 0,please
reindex it.but hot standby server ,it only allow read,not write,
i connect to primary server,i can execute any operation.
standby connects
hello everyone:
my pg version is 9.1.2 running on red hat 5.4 x64 servers.one
day,i found all database indexes can't work,reindex database,it can work,but
some table has primary key,found exists the same two records in table.
primary database error:
version
-
PostgreSQL 9.1.2 on red hat 5.4 x64, compiled by GCC 4.1
There are several tables have two same rows with the same primary key. This
shouldn't happen. Has this been reported as a bug in this version?
--
View this
