Re: Removing PD_ALL_VISIBLE

From: Jeff Davis <pgsql(at)j-davis(dot)com>
To: Pavan Deolasee <pavan(dot)deolasee(at)gmail(dot)com>
Cc: Abhijit Menon-Sen <ams(at)2ndquadrant(dot)com>, Simon Riggs <simon(at)2ndquadrant(dot)com>, pgsql-hackers(at)postgresql(dot)org
Subject: Re: Removing PD_ALL_VISIBLE
Date: 2013-01-17 19:24:46
Message-ID: 1358450686.1953.52.camel@jdavis
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Thu, 2013-01-17 at 10:39 -0800, Jeff Davis wrote:
> On Thu, 2013-01-17 at 15:25 +0530, Pavan Deolasee wrote:
> > Now that I look at the patch, I wonder if there is another fundamental
> > issue with the patch. Since the patch removes WAL logging for the VM
> > set operation, this can happen:
> >
> Thank you.

New patch attached with simple WAL logging.

Regards,
Jeff Davis

Attachment Content-Type Size
rm-pd-all-visible-20130117.patch.gz application/x-gzip 13.4 KB

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2013-01-17 19:31:54 Re: could not create directory "...": File exists
Previous Message Alvaro Herrera 2013-01-17 19:19:38 Re: PATCH: optimized DROP of multiple tables within a transaction