| From: | Alexander Korotkov <aekorotkov(at)gmail(dot)com> |
|---|---|
| To: | pgsql-hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | pg_dump with both --serializable-deferrable and -j |
| Date: | 2015-01-26 09:10:47 |
| Message-ID: | CAPpHfdskrQNzyuTqqtmqPadTg-EpsZ+jhFmREnUcLbNUCmj0MQ@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Hackers,
when pg_dump is run with both --serializable-deferrable and -j options to
pg_dump, it returns errors:
pg_dump: [archiver (db)] query failed: ERROR: a snapshot-importing
transaction must not be READ ONLY DEFERRABLE
pg_dump: [archiver (db)] query failed: ERROR: a snapshot-importing
transaction must not be READ ONLY DEFERRABLE
pg_dump: [archiver (db)] query failed: ERROR: a snapshot-importing
transaction must not be READ ONLY DEFERRABLE
pg_dump: [parallel archiver] query was: SET TRANSACTION SNAPSHOT
'0001E300-1'
pg_dump: [archiver (db)] query failed: ERROR: a snapshot-importing
transaction must not be READ ONLY DEFERRABLE
I've checked it on 9.4.0 and 9.3.5.
So, these options are incompatible now.
Could we start snapshot-importing transaction with repeatable read
isolation level? AFAICS, they should read exactly same data as
snapshot-exporting serializable transaction.
If not, could pg_dump return some more friendly error before actually
trying to dump?
------
With best regards,
Alexander Korotkov.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Andres Freund | 2015-01-26 10:14:05 | SSL renegotiation and other related woes |
| Previous Message | Maciek Sakrejda | 2015-01-26 07:37:42 | Re: Client deadlocks when connecting via ssl |