From: | Simon Riggs <simon(at)2ndQuadrant(dot)com> |
---|---|
To: | Mark Kirkwood <markir(at)paradise(dot)net(dot)nz> |
Cc: | pgsql-hackers <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: Hot standby v5 patch - Databases created post backup remain inaccessible + replica SIGSEGV when coming out of standby |
Date: | 2008-11-04 09:52:41 |
Message-ID: | 1225792361.3971.1072.camel@ebony.2ndQuadrant |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Tue, 2008-11-04 at 18:33 +1300, Mark Kirkwood wrote:
> postgres=# \l
> List of databases
> Name | Owner | Encoding | Collation | Ctype | Access
> Privileges
> -----------+----------+-----------+-----------+-------+-------------------------------------
> bench | postgres | SQL_ASCII | C | C |
> postgres | postgres | SQL_ASCII | C | C |
> template0 | postgres | SQL_ASCII | C | C |
> {=c/postgres,postgres=CTc/postgres}
> template1 | postgres | SQL_ASCII | C | C |
> {=c/postgres,postgres=CTc/postgres}
> (4 rows)
>
> postgres=# \c bench
> FATAL: database "bench" does not exist
> Previous connection kept
CREATE DATABASE didn't trigger the db flat file update, code for which
existed and was triggered in the cases when a transaction would normally
rebuild the flat files. Simple fix, but stupid oversight.
Spotted another problem which is that BuildFlatFile may not be built
consistently if a rebuild is triggered prior to us reaching the recovery
consistency point. This is fixed by forcing a rebuild of the flat files
when we hit the recovery point.
Both one line changes, but I'll go looking for other issues there.
--
Simon Riggs www.2ndQuadrant.com
PostgreSQL Training, Services and Support
From | Date | Subject | |
---|---|---|---|
Next Message | Peter Eisentraut | 2008-11-04 10:36:54 | Re: array_agg (was Re: The Axe list) |
Previous Message | Fujii Masao | 2008-11-04 09:51:42 | Re: Synchronous replication patch v1 |