| From: | "Dave Page" <dpage(at)vale-housing(dot)co(dot)uk> |
|---|---|
| To: | "Neil Conway" <neilc(at)samurai(dot)com>, <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: system info functions |
| Date: | 2006-07-04 07:35:58 |
| Message-ID: | E7F85A1B5FF8D44C8A1AF6885BC9A0E401388D1A@ratbert.vale-housing.co.uk |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
> -----Original Message-----
> From: pgsql-hackers-owner(at)postgresql(dot)org
> [mailto:pgsql-hackers-owner(at)postgresql(dot)org] On Behalf Of Neil Conway
> Sent: 04 July 2006 05:53
> To: pgsql-hackers(at)postgresql(dot)org
> Subject: [HACKERS] system info functions
>
> (1) The docs claim that pg_get_viewdef() returns the "CREATE VIEW
> command for view", but that is clearly not the case:
>
> postgres=# create view v1 as select 1;
> CREATE VIEW
> postgres=# select pg_get_viewdef('v1'::regclass::oid);
> pg_get_viewdef
> ----------------
> SELECT 1;
> (1 row)
>
> Should we change the documentation, or the implementation of
> pg_get_viewdef()?
Documentation, unless we want to break apps that use the function.
Regards, Dave.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Zdenek Kotala | 2006-07-04 09:59:27 | Re: update/insert, delete/insert efficiency WRT vacuum and |
| Previous Message | Dave Page | 2006-07-04 07:32:45 | Re: buildfarm stats |