public inbox for [email protected]  

help / color / mirror / Atom feed

From: Jim C. Nasby <[email protected]>
To: Bruce Momjian <[email protected]>
Cc: PostgreSQL-development <[email protected]>
Cc: PostgreSQL-documentation <[email protected]>
Subject: Re: Updated documentation for new sequence binding
Date: Wed, 5 Oct 2005 13:58:53 -0500
Message-ID: <[email protected]> (raw)
In-Reply-To: <[email protected]>
References: <[email protected]>

On Sun, Oct 02, 2005 at 10:54:10PM -0400, Bruce Momjian wrote:
> pgman wrote:
> > I have marged Tom's description of the new sequence binding with text I
> > was working on.  I modified it to follow the existing "we used to do X,
> > now we do Y" pattern in the surrounding entries:
> > 
> > 	http://candle.pha.pa.us/tmp/pgsql/release.html#RELEASE-8-1
> 
> Sorry, this is a better URL:
> 
> 	http://candle.pha.pa.us/main/writings/pgsql/sgml/release.html#RELEASE-8-1

Out of curiosity, how is this file maintained as development is done?
The reason I'm asking is because it would be nice to have links to more
information, especially for the 'one-liner' items in 1.3.1 for example,
and it seems like that would be easier to do along-the-way rather than
waiting for the end. Even a link to a mailing list discussion would be
better than nothing...

That said, what's

 Improve the optimizer, including auto-resizing of hash joins (Tom)

mean?

On full_page_writes, are we certain that all battery-backed disk caches
ensure that partial-page writes can't happen?

Maybe pg_column_size should just be included in the item for all the
other size functions brought into the backend? If not, ISTM they should
at least be one after the other in the list...

Finally, weren't more changes made it contrib than what's listed?
Nothing's said about pg_autovacuum for example.
-- 
Jim C. Nasby, Sr. Engineering Consultant      [email protected]
Pervasive Software      http://pervasive.com    work: 512-231-6117
vcard: http://jim.nasby.net/pervasive.vcf       cell: 512-569-9461

view thread (6+ messages)  latest in thread

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: [email protected]
  Cc: [email protected], [email protected], [email protected]
  Subject: Re: Updated documentation for new sequence binding
  In-Reply-To: <[email protected]>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by agora; see mirroring instructions
for how to clone and mirror all data and code used for this inbox