Skip site navigation (1) Skip section navigation (2)

Re: Re: [COMMITTERS] pgsql: Fix log_temp_files docs and comments to say bytes not kilobytes.

From: Josh Berkus <josh(at)agliodbs(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Robert Haas <robertmhaas(at)gmail(dot)com>, pgsql-hackers(at)postgresql(dot)org
Subject: Re: Re: [COMMITTERS] pgsql: Fix log_temp_files docs and comments to say bytes not kilobytes.
Date: 2010-07-07 22:48:23
Message-ID: (view raw, whole thread or download thread mbox)
Lists: pgsql-committerspgsql-hackers
On 7/6/10 8:06 AM, Tom Lane wrote:
> It might be that nobody's using any values other than 0 and -1 ...
> in which case it wouldn't matter anyway.  I agree that the lack of
> bug reports is notable.  But still, don't we try to avoid behavioral
> changes in stable branches?

I think most people are doing what I was doing: looking at the values in
the logs, and writing math appropriately.  Most of the other log output
isn't documented well, and the output values are obviously bytes, so
frankly it never occurred to me to check the docs.

Agreed that backporting the fix to 8.3 and 8.4 is infeasible.

                                  -- Josh Berkus
                                     PostgreSQL Experts Inc.

In response to


pgsql-hackers by date

Next:From: Robert HaasDate: 2010-07-07 22:50:07
Subject: Re: Bug? Concurrent COMMENT ON and DROP object
Previous:From: Josh BerkusDate: 2010-07-07 22:44:08
Subject: Re: Proposal for 9.1: WAL streaming from WAL buffers

pgsql-committers by date

Next:From: Tom LaneDate: 2010-07-08 00:14:04
Subject: pgsql: Fix "cannot handle unplanned sub-select" error that can occur
Previous:From: Tom LaneDate: 2010-07-07 21:31:52
Subject: Re: [COMMITTERS] pgsql: Add note that using PL/Python 2 and 3 in the same session will

Privacy Policy | About PostgreSQL
Copyright © 1996-2018 The PostgreSQL Global Development Group