| From: | Peter Eisentraut <peter_e(at)gmx(dot)net> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | Kyle Bateman <kyle(at)actarg(dot)com>, pgsql-sql(at)postgresql(dot)org |
| Subject: | Re: bug in information_schema? |
| Date: | 2005-08-01 08:42:10 |
| Message-ID: | 200508011042.10990.peter_e@gmx.net |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-sql |
Am Samstag, 30. Juli 2005 17:15 schrieb Tom Lane:
> The unconstrained join against pg_user is clearly unnecessary,
> and in fact I took it out a few days ago. I'm not sure whether the
> SELECT DISTINCT is still needed --- it might be, if there can be
> multiple pg_depend entries linking the same entities.
That would have been my guess, but it seems that even if a column or table is
used multiple times, a dependency is recorded only once, as it should be. It
might have been related to the duplicate pg_user mention.
--
Peter Eisentraut
http://developer.postgresql.org/~petere/
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Dawid Kuroczko | 2005-08-01 10:35:15 | Re: How to connect ORACLE database from Postgres function using plpgsql/pltclu? |
| Previous Message | Dinesh Pandey | 2005-08-01 05:31:13 | How to connect ORACLE database from Postgres function using plpgsql/pltclu? |