Re: Commits 8de72b and 5457a1 (COPY FREEZE)
Simon Riggs <simon@2ndquadrant.com>
From: Simon Riggs <simon@2ndQuadrant.com>
To: Jeff Davis <pgsql@j-davis.com>
Cc: pgsql-hackers@postgresql.org
Date: 2012-12-07T16:16:14Z
Lists: pgsql-hackers
On 4 December 2012 20:38, Jeff Davis <pgsql@j-davis.com> wrote: > Even if it is, I would > think that a sufficiently narrow case -- such as CTAS outside of a > transaction block -- would be safe CTAS would be safe to do that with. CLUSTER and VACUUM FULL are already done. Outside of a transaction block would be automatic. Inside of a transaction block we could use a parameter called initially_frozen. This would act same as FREEZE on COPY. Parameter would not be recorded into the reloptions field on pg_class, since it is a one-time option and has no meaning after end of xact. > along with some slightly broader > cases (like BEGIN; CREATE TABLE; INSERT/COPY). Historically we've chosen not to allow bulk insert options on INSERT, so that is a separate discussion. -- Simon Riggs http://www.2ndQuadrant.com/ PostgreSQL Development, 24x7 Support, Training & Services
Commits
Same data as JSON:
GET /api/v1/messages/:b64id/commits
the thread's linked commits as JSON, with link sources.
API reference →
-
Keep rd_newRelfilenodeSubid across overflow.
- ae9aba69a860 9.3.0 cited
-
Reduce scope of changes for COPY FREEZE.
- 5457a130d3a6 9.3.0 cited
-
COPY FREEZE and mark committed on fresh tables.
- 8de72b66a2ed 9.3.0 cited