This has been saved for the 8.4 release:
http://momjian.postgresql.org/cgi-bin/pgpatches_hold
---
Josh Berkus wrote:
> All,
>
> I'm working on cleaning up postgresql.conf and pg_settings for the
> release. Attach
Bruce,
> Josh, is any of this happening for 8.3?
Hmmm, just the format cleanup. I haven't heard any objections, but I haven't
heard any comments on the underlying broken functionality either (like
seq_scan_cost), which are beyond me to fix.
Patch next week.
--
Josh Berkus
PostgreSQL @ Sun
S
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Bruce Momjian wrote:
> Josh, is any of this happening for 8.3?
Should I run with this or let it lay?
>
> ---
>
> Josh Berkus wrote:
>> All,
>>
>> I'm working on cleaning up pos
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Bruce Momjian wrote:
> Josh, is any of this happening for 8.3?
I would be willing to take a stab at this and submit by Monday.
Joshua D. Drake
>
> ---
>
> Josh Berkus wrote:
Josh, is any of this happening for 8.3?
---
Josh Berkus wrote:
> All,
>
> I'm working on cleaning up postgresql.conf and pg_settings for the
> release. Attached is a sample WIP. It's not in patch form because I'm
> not
Am Montag, 2. Juli 2007 13:03 schrieb Josh Berkus:
> (change requires restart): this phrase appears over 20 times in the
> notes. This is enough times to be really repetitive and take up a lot
> of scrolling space, while not actually covering all startup-time
> parameters.
Which ones are missing?
Greg Smith <[EMAIL PROTECTED]> writes:
> On Mon, 2 Jul 2007, Tom Lane wrote:
>>> # wal_buffers = 1MB
>> Is there really evidence in favor of such a high setting for this,
>> either?
> I noticed consistant improvements in throughput on pgbench results with
> lots of clients going from the default
On Mon, 2 Jul 2007, Tom Lane wrote:
# wal_buffers = 1MB
Is there really evidence in favor of such a high setting for this,
either?
I noticed consistant improvements in throughput on pgbench results with
lots of clients going from the default to 256KB, flatlining above that; it
seemed suffic
Tom Lane wrote:
(change requires restart): this phrase appears over 20 times in the
notes. This is enough times to be really repetitive and take up a lot
of scrolling space, while not actually covering all startup-time
parameters. We should either (a) remove all such notes and rely on
docs,
Josh Berkus <[EMAIL PROTECTED]> writes:
>> I'm working on cleaning up postgresql.conf and pg_settings for the
>> ...
>> seq_scan_cost: this is independant of all of the other _costs.
So? All the other costs are independent of it, too. I don't understand
what problem you have with it.
>> (chan
On Jul 2, 2007, at 6:03 AM, Josh Berkus wrote:
(change requires restart): this phrase appears over 20 times in the
notes. This is enough times to be really repetitive and take up a
lot of scrolling space, while not actually covering all startup-
time parameters. We should either (a) remove
This time *with* the attachment.
All,
I'm working on cleaning up postgresql.conf and pg_settings for the
release. Attached is a sample WIP. It's not in patch form because I'm
not done yet; I've just been editing postgresql.conf and need to fix the
docs and pg_settings to match.
Issues
All,
I'm working on cleaning up postgresql.conf and pg_settings for the
release. Attached is a sample WIP. It's not in patch form because I'm
not done yet; I've just been editing postgresql.conf and need to fix the
docs and pg_settings to match.
Issues encountered and changes made:
Postgr
13 matches
Mail list logo
