Re: --single-transaction hack to pg_upgrade does not work

Tom Lane <tgl@sss.pgh.pa.us>

From: Tom Lane <tgl@sss.pgh.pa.us>
To: Andres Freund <andres@2ndquadrant.com>
Cc: Bruce Momjian <bruce@momjian.us>, Andrew Dunstan <andrew@dunslane.net>, pgsql-hackers@postgresql.org
Date: 2012-12-01T19:13:29Z
Lists: pgsql-hackers
Andres Freund <andres@2ndquadrant.com> writes:
> On 2012-12-01 13:43:44 -0500, Bruce Momjian wrote:
>> I believe this text in alter_type.sgml need updating:
>> 
>> <command>ALTER TYPE ... ADD VALUE</> (the form that adds a new value to an
>> enum type) cannot be executed inside a transaction block.

> I purposefully didn't change that because the new support is rather
> minimalistic.

Yeah, I tend to agree.  There are a lot of cases that people might think
should work that won't, and anyway it's not clear what the use-case is
for this beyond pg_dump's very specific usage.

			regards, tom lane


Commits

Same data as JSON: GET /api/v1/messages/:b64id/commits the thread's linked commits as JSON, with link sources. API reference →
  1. In pg_upgrade, dump each database separately and use