I second that.
I have discussed adding partitioning tables almost a year ago...
No need to partition a functional index or anything like that.
Just partition on a specific field.
Ron Johnson wrote:
>[...]
> Partitioning "should" be put on the TODO list soon after tablespaces
> (or DBA-defined dir
On Fri, 1 Aug 2003, Roger Hand wrote:
> We are moving an application from Oracle 8i to Postgres and I've run
> into a problem attempting to duplicate a feature we currently use.
>
> In Oracle you can divide a table into partitions. We use this feature
> to break up the data by month. Each mont
Did you think about cluster on index ?
[EMAIL PROTECTED] wrote:
I am looking at ways to speed up queries, the most common way by for
queries to be constrianed is by date range. I have indexed the date
column. Queries are still slower than i would like.
Would there be any performance increase f
You could create an index on the function date(), which strips the time
information.
> -Original Message-
> From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
> Sent: 04 August 2003 14:01
> To: PgSQL General ML
> Subject: Re: [GENERAL] Monthly table partitioning for fast pu
I am looking at ways to speed up queries, the most common way by for
queries to be constrianed is by date range. I have indexed the date
column. Queries are still slower than i would like.
Would there be any performance increase for these types of queries if
the tables were split by month as de
On Fri, Aug 01, 2003 at 01:46:54PM -0700, Roger Hand wrote:
> We are moving an application from Oracle 8i to Postgres and I've run into
> a problem attempting to duplicate a feature we currently use.
>
> In Oracle you can divide a table into partitions. We use this feature to
> break up the data b
