Request a Demo
Home   >   mailing lists

Re: Automating Partitions in PostgreSQL - Query on syntax - Mailing list pgsql-hackers

From Kedar Potdar
Subject Re: Automating Partitions in PostgreSQL - Query on syntax
Date
Msg-id bd8134a40904210638i2ba08c5aofc3740e21dc9ecb9@mail.gmail.com
Whole thread Raw
In response to Re: Automating Partitions in PostgreSQL - Query on syntax  (Greg Stark <stark@enterprisedb.com>)
Responses Re: Automating Partitions in PostgreSQL - Query on syntax
List pgsql-hackers
Tree view
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@enterprisedb.com> wrote:
On Tue, Apr 21, 2009 at 12:50 PM, Kedar Potdar <kedar.potdar@gmail.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

pgsql-hackers by date:

Previous
From: Heikki Linnakangas
Date:
Subject: Re: New trigger option of pg_standby
Next
From: "Dickson S. Guedes"
Date:
Subject: Re: Automating Partitions in PostgreSQL - Query on syntax