Re: logical changeset generation v6.2 - Mailing list pgsql-hackers

From Heikki Linnakangas
Subject Re: logical changeset generation v6.2
Date
Msg-id 5266A587.1020306@vmware.com
Whole thread Raw
In response to Re: logical changeset generation v6.2  (Andres Freund <andres@2ndquadrant.com>)
Responses Re: logical changeset generation v6.2
List pgsql-hackers
On 22.10.2013 19:12, Andres Freund wrote:
> On 2013-10-18 20:26:16 +0200, Andres Freund wrote:
>> 4) Store both (cmin, cmax) for catalog tuples.
>
> BTW: That would have the nice side-effect of delivering the basis of
> what you need to do parallel sort in a transaction that previously has
> performed DDL.
>
> Currently you cannot do anything in parallel after DDL, even if you only
> scan the table in one backend, because operators et al. have to do
> catalog lookups which you can't do consistently since cmin/cmax aren't
> available in both.

Parallel workers will need cmin/cmax for user tables too, to know which 
tuples are visible to the snapshot.

- Heikki



pgsql-hackers by date:

Previous
From: Andres Freund
Date:
Subject: Re: logical changeset generation v6.2
Next
From: Andres Freund
Date:
Subject: Re: logical changeset generation v6.2