| From: | Michael Paquier <michael(dot)paquier(at)gmail(dot)com> |
|---|---|
| To: | David Fetter <david(at)fetter(dot)org> |
| Cc: | Peter van Hardenberg <pvh(at)pvh(dot)ca>, "pgsql-hackers(at)postgresql(dot)org Hackers" <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Synchronous commit not... synchronous? |
| Date: | 2012-11-01 04:31:34 |
| Message-ID: | CAB7nPqSB7jKFTo-3poco3vZv66VUc_1Xs2k0wz3PkyCQNc1pVw@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Thu, Nov 1, 2012 at 1:03 PM, David Fetter <david(at)fetter(dot)org> wrote:
> On Wed, Oct 31, 2012 at 06:39:20PM -0700, Peter van Hardenberg wrote:
> > This was rather surprising - my synchronous commit was... not
> > cancelled. Is this expected behaviour?
>
> I believe it is.
>
> Does the following do the right thing?
>
> SET synchronous_commit='on';
> BEGIN;
> INSERT INTO data VALUES ('baz');
> COMMIT;^c
>
> Oh, and how did you get that cancel in?
>
He enforced a manual cancel from client with something like Ctrl+C to
cancel query.
In this case you do not wait for the slave to confirm that the commit
information has been flushed on its disk.
--
Michael Paquier
http://michael.otacoo.com
| From | Date | Subject | |
|---|---|---|---|
| Next Message | David Fetter | 2012-11-01 04:48:13 | Re: Synchronous commit not... synchronous? |
| Previous Message | Amit kapila | 2012-11-01 04:14:18 | Re: alter table tablename add column - breaks pl/pgsql function returns tablename |