Re: --single-transaction hack to pg_upgrade does not work
Bruce Momjian <bruce@momjian.us>
From: Bruce Momjian <bruce@momjian.us>
To: Andres Freund <andres@2ndquadrant.com>
Cc: Andrew Dunstan <andrew@dunslane.net>, Tom Lane <tgl@sss.pgh.pa.us>, pgsql-hackers@postgreSQL.org
Date: 2012-12-01T17:05:32Z
Lists: pgsql-hackers
On Sat, Dec 1, 2012 at 05:36:20PM +0100, Andres Freund wrote: > On 2012-12-01 17:03:03 +0100, Andres Freund wrote: > > Could we possibly allow adding enum values to a type which was just created in > > this transaction? That shouldn't be too hard. At least easier than providing > > the capability to pre-assign the next N oids... > > The attached patch does just that. Its *not* ready yet though, as it > will be apparent for everyone who reads it ;) > > To really make that work in a reliable manner we would probably need > an rd_createSubid for typcache entries instead of testing xmin as I have > done here? I can confirm that this patch allows pg_upgrade's test.sh to pass. :-) -- Bruce Momjian <bruce@momjian.us> http://momjian.us EnterpriseDB http://enterprisedb.com + It's impossible for everything to be true. +
Commits
Same data as JSON:
GET /api/v1/messages/:b64id/commits
the thread's linked commits as JSON, with link sources.
API reference →
-
In pg_upgrade, dump each database separately and use
- 12ee6ec71f87 9.3.0 cited