| From: | Fujii Masao <masao(dot)fujii(at)gmail(dot)com> |
|---|---|
| To: | Greg Smith <greg(at)2ndquadrant(dot)com> |
| Cc: | pgsql-admin(at)postgresql(dot)org |
| Subject: | Re: replication_timeout does not seem to be working |
| Date: | 2011-07-27 09:16:59 |
| Message-ID: | CAHGQGwFRj9PFQBMAQGVFrENYsUjo20YxGo5+GdpGexGfpDQguQ@mail.gmail.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-admin |
On Wed, Jul 27, 2011 at 3:47 PM, Greg Smith <greg(at)2ndquadrant(dot)com> wrote:
> On 07/22/2011 12:11 PM, A J wrote:
>
> Basically I wish my synchronous write transaction to not wait indefinitely
> when the synchronous standby servers are not available. But rather a
> response returned back to client that write could not be successful, after
> trying for 'n' seconds. How can that be accomplished ?
>
> You might be able to get what you want here by setting statement_timeout to
> 'n' seconds when doing a write transaction.
No. statement_timeout cannot cancel the transaction whose commit record has
already been written to local disk.
Regards,
--
Fujii Masao
NIPPON TELEGRAPH AND TELEPHONE CORPORATION
NTT Open Source Software Center
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Glyn Astill | 2011-07-27 16:27:23 | Adding line to pg_hba.conf for a specific group makes superuser authentication fail in 9.0? |
| Previous Message | Benjamin Knoth | 2011-07-27 08:41:28 | HA-Fedora repository with HA-Postgresql |