Re: pg_filedump 9.3: checksums (and a few other fixes)

From: Peter Geoghegan <pg(at)heroku(dot)com>
To: Jeff Davis <pgsql(at)j-davis(dot)com>
Cc: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, pgsql-hackers(at)postgresql(dot)org
Subject: Re: pg_filedump 9.3: checksums (and a few other fixes)
Date: 2013-06-27 07:10:28
Message-ID: CAM3SWZSOpDqL2KrE3RxujmVb9JF8V_xs6hmuzkd3gsDEOHh6Qg@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Thu, Jun 27, 2013 at 12:07 AM, Peter Geoghegan <pg(at)heroku(dot)com> wrote:
>> I'm not sure what the resolution of Alvaro's concern was, so I left the
>> flag reporting the same as the previous patch.
>
> Alvaro's concern was that the new flags added (those added by the
> foreign key locks patch) do something cute with re-using multiple
> other bits in an otherwise nonsensical combination to represent a
> distinct state.

I just realized that it wasn't that you didn't understand the nature
of the problem, but that you weren't sure of a resolution. Sorry for
the noise.

--
Peter Geoghegan

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Hitoshi Harada 2013-06-27 07:12:07 Re: refresh materialized view concurrently
Previous Message Yuri Levinsky 2013-06-27 07:08:08 Re: Hash partitioning.