public inbox for [email protected]
help / color / mirror / Atom feedPostgreSQL.conf / runtime docs
5+ messages / 4 participants
[nested] [flat]
* PostgreSQL.conf / runtime docs
@ 2004-08-06 16:42 Josh Berkus <[email protected]>
2004-08-06 17:14 ` Re: PostgreSQL.conf / runtime docs Tom Lane <[email protected]>
2004-08-09 17:40 ` Re: PostgreSQL.conf / runtime docs Peter Eisentraut <[email protected]>
0 siblings, 2 replies; 5+ messages in thread
From: Josh Berkus @ 2004-08-06 16:42 UTC (permalink / raw)
To: pgsql-docs
Folks,
I want to put some serious work into these. However, I won't have all the
data I need to update them until we're close to release; I need to do some
serious performance testing on 8.0beta so that I can have actual numbers to
recommend.
As we've always accepted doc patches up until a few days before release, this
shouldn't be a problem, yes? (Besides, I still need to fix the SGML
libraries on my laptop ... )
--
Josh Berkus
Aglio Database Solutions
San Francisco
^ permalink raw reply [nested|flat] 5+ messages in thread
* Re: PostgreSQL.conf / runtime docs
2004-08-06 16:42 PostgreSQL.conf / runtime docs Josh Berkus <[email protected]>
@ 2004-08-06 17:14 ` Tom Lane <[email protected]>
2004-08-06 19:25 ` Re: PostgreSQL.conf / runtime docs Bruce Momjian <[email protected]>
1 sibling, 1 reply; 5+ messages in thread
From: Tom Lane @ 2004-08-06 17:14 UTC (permalink / raw)
To: Josh Berkus <[email protected]>; +Cc: pgsql-docs
Josh Berkus <[email protected]> writes:
> As we've always accepted doc patches up until a few days before
> release, this shouldn't be a problem, yes?
I'd be really surprised if anyone wants to change that policy.
regards, tom lane
^ permalink raw reply [nested|flat] 5+ messages in thread
* Re: PostgreSQL.conf / runtime docs
2004-08-06 16:42 PostgreSQL.conf / runtime docs Josh Berkus <[email protected]>
2004-08-06 17:14 ` Re: PostgreSQL.conf / runtime docs Tom Lane <[email protected]>
@ 2004-08-06 19:25 ` Bruce Momjian <[email protected]>
0 siblings, 0 replies; 5+ messages in thread
From: Bruce Momjian @ 2004-08-06 19:25 UTC (permalink / raw)
To: Tom Lane <[email protected]>; +Cc: Josh Berkus <[email protected]>; pgsql-docs
Tom Lane wrote:
> Josh Berkus <[email protected]> writes:
> > As we've always accepted doc patches up until a few days before
> > release, this shouldn't be a problem, yes?
>
> I'd be really surprised if anyone wants to change that policy.
Agreed. We take doc improvements anytime!
--
Bruce Momjian | http://candle.pha.pa.us
[email protected] | (610) 359-1001
+ If your life is a hard drive, | 13 Roberts Road
+ Christ can be your backup. | Newtown Square, Pennsylvania 19073
^ permalink raw reply [nested|flat] 5+ messages in thread
* Re: PostgreSQL.conf / runtime docs
2004-08-06 16:42 PostgreSQL.conf / runtime docs Josh Berkus <[email protected]>
@ 2004-08-09 17:40 ` Peter Eisentraut <[email protected]>
2004-08-09 20:53 ` Re: PostgreSQL.conf / runtime docs Josh Berkus <[email protected]>
1 sibling, 1 reply; 5+ messages in thread
From: Peter Eisentraut @ 2004-08-09 17:40 UTC (permalink / raw)
To: Josh Berkus <[email protected]>; pgsql-docs
Josh Berkus wrote:
> As we've always accepted doc patches up until a few days before
> release, this shouldn't be a problem, yes? (Besides, I still need to
> fix the SGML libraries on my laptop ... )
If you plan to do major outline reorganizations, I suggest that you do
them somewhat sooner than a few days before release, because there is
also a release management effort involved in the documentation. But
you can always plug in your latest measurements any time.
--
Peter Eisentraut
http://developer.postgresql.org/~petere/
^ permalink raw reply [nested|flat] 5+ messages in thread
* Re: PostgreSQL.conf / runtime docs
2004-08-06 16:42 PostgreSQL.conf / runtime docs Josh Berkus <[email protected]>
2004-08-09 17:40 ` Re: PostgreSQL.conf / runtime docs Peter Eisentraut <[email protected]>
@ 2004-08-09 20:53 ` Josh Berkus <[email protected]>
0 siblings, 0 replies; 5+ messages in thread
From: Josh Berkus @ 2004-08-09 20:53 UTC (permalink / raw)
To: Peter Eisentraut <[email protected]>; pgsql-docs
Peter,
> If you plan to do major outline reorganizations, I suggest that you do
> them somewhat sooner than a few days before release, because there is
> also a release management effort involved in the documentation. But
> you can always plug in your latest measurements any time.
No massive re-org, we did that last version.
No, here's what I want to do:
1) add a new section at the top of the docs describing the most common options
that people want to set on a new installation.
2) Add notes to each item about how to decide what to set it at.
3) Add label/values for:
Default Value:
Set At: (when you can change it)
(this latter information is there but buried in the text; it would be better
put on a seperate line)
4) add notes regarding version changes (like that work_mem used to be
sort_mem, and that add_missing_from will default to "false" next version)
Your recommendations on tagging stuff are highly welcome; I'm still
uncomfortable with SGML.
--
Josh Berkus
Aglio Database Solutions
San Francisco
^ permalink raw reply [nested|flat] 5+ messages in thread
end of thread, other threads:[~2004-08-09 20:53 UTC | newest]
Thread overview: 5+ messages (download: mbox mbox.gz follow: Atom feed)
-- links below jump to the message on this page --
2004-08-06 16:42 PostgreSQL.conf / runtime docs Josh Berkus <[email protected]>
2004-08-06 17:14 ` Tom Lane <[email protected]>
2004-08-06 19:25 ` Bruce Momjian <[email protected]>
2004-08-09 17:40 ` Peter Eisentraut <[email protected]>
2004-08-09 20:53 ` Josh Berkus <[email protected]>
This inbox is served by agora; see mirroring instructions
for how to clone and mirror all data and code used for this inbox