Re: Summary and Plan for Hot Standby - Mailing list pgsql-hackers

From Tom Lane
Subject Re: Summary and Plan for Hot Standby
Date
Msg-id 14784.1258644282@sss.pgh.pa.us
Whole thread Raw
In response to Re: Summary and Plan for Hot Standby  (Heikki Linnakangas <heikki.linnakangas@enterprisedb.com>)
Responses Re: Summary and Plan for Hot Standby
List pgsql-hackers
Heikki Linnakangas <heikki.linnakangas@enterprisedb.com> writes:
> Tatsuo Ishii wrote:
>> Sorry for confusion. My example is under normal PostgreSQL, not under
>> HS enabled.

> You get the same result in standby:

AFAICT Tatsuo's example just shows that we might wish to add a check
for read-only transaction mode before parsing an INSERT/UPDATE/DELETE
command.  But it seems relatively minor in any case --- at the worst
you'd get an unexpected error message, no?
        regards, tom lane


pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: Rejecting weak passwords
Next
From: Heikki Linnakangas
Date:
Subject: Re: Summary and Plan for Hot Standby