From: | NikhilS <nikkhils(at)gmail(dot)com> |
---|---|
To: | "Guillaume Smet" <guillaume(dot)smet(at)gmail(dot)com> |
Cc: | "Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us>, pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: Idle idea for a feature |
Date: | 2007-04-11 05:39:12 |
Message-ID: | d3c4af540704102239r46948549uc121af1d3ecfbf10@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Hi,
On 4/11/07, Guillaume Smet <guillaume(dot)smet(at)gmail(dot)com> wrote:
>
> On 4/10/07, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> > ISTM it'd be a good idea if it did, as "are there any incoming
> > foreign keys" seems to be a question we constantly ask when solving
> > update-performance problems, and there isn't any easy way to check for
> > such.
>
> On similar lines, maybe \d can also show the list of inheritors when
invoked on a parent.
e.g:
postgres=# \d parent
Table "public.parent"
Column | Type | Modifiers
--------+---------+-----------
a | integer |
Indexes:
"parent_a_key" UNIQUE, btree (a)
Inherited by: child
Regards,
Nikhils
--
EnterpriseDB http://www.enterprisedb.com
From | Date | Subject | |
---|---|---|---|
Next Message | Kris Kennaway | 2007-04-11 05:40:49 | Re: [mux@FreeBSD.org: Re: Anyone interested in improving postgresql scaling?] |
Previous Message | Hannu Krosing | 2007-04-11 05:33:32 | Re: [HACKERS] Full page writes improvement, code update |