| From: | Richard Broersma <richard(dot)broersma(at)gmail(dot)com> |
|---|---|
| To: | Josh Berkus <josh(at)agliodbs(dot)com> |
| Cc: | Darren Duncan <darren(at)darrenduncan(dot)net>, postgres hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: SQL command to edit postgresql.conf, with comments |
| Date: | 2010-10-12 23:07:10 |
| Message-ID: | AANLkTi=gubEWtUF71xxxP7PKQyP9d6sNTDs0J7QJS4S=@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Tue, Oct 12, 2010 at 3:54 PM, Josh Berkus <josh(at)agliodbs(dot)com> wrote:
> Oh. Now that's an interesting perspective ... you're suggesting that we
> take the comments and apply them as COMMENTS on the specific pg_settings?
On a side note regarding comments, I'd like to make a request for a
more comprehensive commenting mechanism. The first though that comes
to my mind would allow for comments to be stored and annotated using
XML or sgml. It'd be nice to be able to generate user documentation
from selected comments taken from application derived database
objects.
I don't know, maybe this is already possible.
--
Regards,
Richard Broersma Jr.
Visit the Los Angeles PostgreSQL Users Group (LAPUG)
http://pugs.postgresql.org/lapug
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2010-10-12 23:10:08 | Re: Review: Fix snapshot taking inconsistencies |
| Previous Message | Josh Berkus | 2010-10-12 22:54:21 | Re: SQL command to edit postgresql.conf, with comments |