Re: Dynamic Partitioning using Segment Visibility Maps

From: Markus Schiltknecht <markus(at)bluegap(dot)ch>
To: Andrew Sullivan <ajs(at)crankycanuck(dot)ca>, pgsql-hackers(at)postgresql(dot)org
Subject: Re: Dynamic Partitioning using Segment Visibility Maps
Date: 2008-01-05 10:13:12
Message-ID: 477F5838.7010904@bluegap.ch
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Andrew Sullivan wrote:
> On Fri, Jan 04, 2008 at 10:26:54PM +0100, Markus Schiltknecht wrote:
>> I'm still puzzled about how a DBA is expected to figure out which
>> segments to mark.
>
> I think that part might be hand-wavy still. But once this facility is
> there, what's to prevent the current active segment (and the rest) from also
> getting this mark, which would mean "the table is read only"?

Well, sure, marking *all* segments read-only is pretty easy. But that
was not quite my point.

Regards

Markus

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Jari Aalto 2008-01-05 11:33:39 [PATCH] pg_hba.conf.sample: mention www.postgresql.org
Previous Message Simon Riggs 2008-01-05 09:33:45 Re: Dynamic Partitioning using Segment Visibility Maps