From: | Toby Corkindale <toby(dot)corkindale(at)strategicdata(dot)com(dot)au> |
---|---|
To: | Shoaib Mir <shoaibmir(at)gmail(dot)com> |
Cc: | pgsql-general(at)postgresql(dot)org |
Subject: | Re: Indexes on inheriting tables |
Date: | 2011-08-25 02:24:56 |
Message-ID: | 4E55B278.5080106@strategicdata.com.au |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On 25/08/11 12:10, Shoaib Mir wrote:
> On Thu, Aug 25, 2011 at 11:57 AM, Toby Corkindale
> <toby(dot)corkindale(at)strategicdata(dot)com(dot)au
> <mailto:toby(dot)corkindale(at)strategicdata(dot)com(dot)au>> wrote:
>
>
> It seems messy to inherit the columns but not the indexes or checks
> upon them :(
>
>
>
> Yes it can be a bit annoying at timse but you can try to automate the
> whole process as well. Like I found this blog entry -->
> http://blog.inovia.fr/auto-partitioning-on-postgresql-part-1/
As far as I could tell, that isn't automating anything to do with
indexes or checks on the child tables?
Although using a trigger to automate the creation of the child table
itself is still nifty. I hadn't thought of that.
thanks,
Toby
From | Date | Subject | |
---|---|---|---|
Next Message | Ondrej Ivanič | 2011-08-25 02:44:23 | Re: Indexes on inheriting tables |
Previous Message | Royce Ausburn | 2011-08-25 02:19:15 | Re: Collapsing multiple subqueries into one |