Re: Automating Partitions in PostgreSQL - Query on syntax

From: Kedar Potdar <kedar(dot)potdar(at)gmail(dot)com>
To: Greg Stark <stark(at)enterprisedb(dot)com>, pgsql-hackers(at)postgresql(dot)org
Subject: Re: Automating Partitions in PostgreSQL - Query on syntax
Date: 2009-04-21 13:38:18
Message-ID: bd8134a40904210638i2ba08c5aofc3740e21dc9ecb9@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Hi Greg,

Thanks for your response.

Currently, such records are left in the overflow partition and its
responsibility
of user to insert them into partitioned-table which will then re-direct
those to
appropriate partitions.

Regards,
--
Kedar.

On Tue, Apr 21, 2009 at 5:29 PM, Greg Stark <stark(at)enterprisedb(dot)com> wrote:

> On Tue, Apr 21, 2009 at 12:50 PM, Kedar Potdar <kedar(dot)potdar(at)gmail(dot)com>
> wrote:
> > I want to seek general opinion from the community on preferences between
> > user-friendly ‘Oracle’ syntax, and a more generic syntax that allows
> ‘gaps’
> > in partition ranges?
>
>
> What happens to records in the overflow table when you add a new
> partition whose range covers their values?
>
> --
> greg
>

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Dickson S. Guedes 2009-04-21 13:46:41 Re: Automating Partitions in PostgreSQL - Query on syntax
Previous Message Heikki Linnakangas 2009-04-21 12:55:10 Re: New trigger option of pg_standby