Postgres Pro
Downloads
Home   >   mailing lists

Re: Should pg_export_snapshot() and currtid() be tagged parallel-unsafe? - Mailing list pgsql-hackers

From Robert Haas
Subject Re: Should pg_export_snapshot() and currtid() be tagged parallel-unsafe?
Date
Msg-id CA+Tgmob0jYwkagx110W-433BsMKN5Z9wuGwqsr1Hbycee5hPow@mail.gmail.com
Whole thread Raw
In response to Should pg_export_snapshot() and currtid() be tagged parallel-unsafe?  (Andreas Seltenreich <seltenreich@gmx.de>)
List pgsql-hackers
Tree view 
On Tue, Jun 14, 2016 at 5:01 PM, Andreas Seltenreich <seltenreich@gmx.de> wrote:
> Digging through the sqlsmith logging db, I noticed the following errors:
>
>     ERROR:  cannot update SecondarySnapshot during a parallel operation
>     ERROR:  cannot assign XIDs during a parallel operation
>
> Queries raising the first one always contain calls to currtid() or
> currtid2().  Queries raising the second one always contain a call to
> pg_export_snapshot().  Patch to tag them as unsafe attached.

Thanks, committed.

None of these are exercised by 'make check', or this would have been
caught sooner.

-- 
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company

pgsql-hackers by date:

Previous
From: Noah Misch
Date:
Subject: Re: Should phraseto_tsquery('simple', 'blue blue') @@ to_tsvector('simple', 'blue') be true ?
Next
From: Robert Haas
Date:
Subject: Re: Re: [COMMITTERS] pgsql: Avoid extra locks in GetSnapshotData if old_snapshot_threshold <