From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Joe Conway <mail(at)joeconway(dot)com> |
Cc: | Patches <pgsql-patches(at)postgresql(dot)org> |
Subject: | Re: pg_settings view |
Date: | 2002-08-11 00:33:39 |
Message-ID: | 17657.1029026019@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-patches |
Joe Conway <mail(at)joeconway(dot)com> writes:
> The attached patch takes advantage of this, moving
> show_all_settings() from contrib/tablefunc into the backend (renamed
> all_settings().
That change of name seems like a step backwards to me; it's not more
intuitive, and it does seem more likely to conflict with user functions.
Actually, if this is going to be primarily a support function for a
view, I wonder if it should be pg_show_all_settings.
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Joe Conway | 2002-08-11 01:14:07 | Re: pg_settings view |
Previous Message | Joe Conway | 2002-08-10 22:56:02 | pg_settings view |