From: | Simon Riggs <simon(at)2ndQuadrant(dot)com> |
---|---|
To: | "David F(dot) Skoll" <dfs(at)roaringpenguin(dot)com> |
Cc: | pgsql-admin <pgsql-admin(at)postgresql(dot)org> |
Subject: | Re: Hot-standby and canceled queries |
Date: | 2013-04-24 13:01:13 |
Message-ID: | CA+U5nMKFaOcr2GAnr6m7P1e_YduX-sj5U8ZSyhXDO26KCuBRow@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-admin |
On 24 April 2013 12:42, David F. Skoll <dfs(at)roaringpenguin(dot)com> wrote:
> I ran a query on a hot-standby (PostgreSQL 9.1) and it was canceled as
> per the documentation about vacuum cleanups on the master.
>
> Second time testing, I started a transaction on the master (with
> BEGIN) but my query on the hot-standby was still canceled.
>
> Is that because a transaction doesn't "really" begin with BEGIN, but only
> after the first real statement after the BEGIN? Is it sufficient to
> use: BEGIN; SELECT ... ; to start a transaction on the master
Yes
>, or
> do I need to use UPDATE or INSERT to ensure that a vacuum cleanup isn't
> applied until the transaction is finished?
SELECT is sufficient
--
Simon Riggs http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Training & Services
From | Date | Subject | |
---|---|---|---|
Next Message | David F. Skoll | 2013-04-24 15:34:16 | Re: Hot-standby and canceled queries |
Previous Message | David F. Skoll | 2013-04-24 11:42:38 | Hot-standby and canceled queries |