Re: Remaining beta blockers - Mailing list pgsql-hackers

From Stephen Frost
Subject Re: Remaining beta blockers
Date
Msg-id 20130430014411.GF4361@tamriel.snowman.net
Whole thread Raw
In response to Re: Remaining beta blockers  (Kevin Grittner <kgrittn@ymail.com>)
Responses Re: Remaining beta blockers
List pgsql-hackers
* Kevin Grittner (kgrittn@ymail.com) wrote:
> If they modified the heap files that way while the server was
> running, the results would be somewhat unpredictable.  If they did
> it while the server was stopped, starting the server and attempting
> to access the matview would generate:

Right, the point being that they could (ab)use it as a flag to trigger
something to happen.  I'd also be worried about failure cases where
files appear to be zero-length.

> > Or we end up wanting to have that file be non-zero and considered
> > 'empty' later, but we don't want pg_upgrade running around
> > touching all of the existing files out there?
>
> I didn't follow this one; could you restate it, please?

Down the road we decide that we shouldn't have any zero-length files
(perhaps due to checksums..?), yet we have to special case around these
mat views and figure out a way to deal with them during pg_upgrade.
Thanks,
    Stephen

pgsql-hackers by date:

Previous
From: Robert Haas
Date:
Subject: Re: The missing pg_get_*def functions
Next
From: Peter Eisentraut
Date:
Subject: Re: pg_ctl non-idempotent behavior change