From: | Hannu Krosing <hannu(at)krosing(dot)net> |
---|---|
To: | Robert Haas <robertmhaas(at)gmail(dot)com> |
Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: cheaper snapshots |
Date: | 2011-07-28 23:29:54 |
Message-ID: | 1311895794.3117.1614.camel@hvost |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Thu, 2011-07-28 at 16:42 -0400, Robert Haas wrote:
> On Thu, Jul 28, 2011 at 4:36 PM, Hannu Krosing <hannu(at)krosing(dot)net> wrote:
> > so in case of stuck slave the syncrep transcation is committed after
> > crash, but is not committed before the crash happens ?
>
> Yep.
>
> > ow will the replay process get stuc gaian during recovery ?
>
> Nope.
Are you sure ? I mean the case when a stuck master comes up but slave is
still not functional.
How does this behavior currently fit in with ACID and sync guarantees ?
> --
> Robert Haas
> EnterpriseDB: http://www.enterprisedb.com
> The Enterprise PostgreSQL Company
>
From | Date | Subject | |
---|---|---|---|
Next Message | Robert Haas | 2011-07-28 23:45:01 | Re: error: could not find pg_class tuple for index 2662 |
Previous Message | Robert Haas | 2011-07-28 23:20:04 | Re: cheaper snapshots |