On Fri, Jun 25, 2010 at 1:56 PM, Josh Berkus <josh(at)agliodbs(dot)com> wrote:
>
>>> Shouldn't this be backpatched, or was this a new bug in 9.0?
>
> We've always output bytes. I'd have noticed the discrepancy myself if I'd
> read the actual docs ;-)
>
> KB would be more useful. And I don't think people have enough scripts built
> on this yet to make this break anything. We should backport to 8.4.
log_temp_files was introduced in 8.3, so we'll need to backpatch this
to 8.3, not just 8.4. Greg Smith tells me Simon has been busy with
other things, so I'm going to pick this up. Barring objections, I'm
going to revert Simon's patch and change the behavior instead, per the
attached patch. I will also back-patch the fix to 8.4 and 8.3.
--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise Postgres Company
In response to
Responses
pgsql-hackers by date
| Next: | From: Tom Lane | Date: 2010-07-06 14:33:18 |
| Subject: Re: Bug? Concurrent COMMENT ON and DROP object |
| Previous: | From: Robert Haas | Date: 2010-07-06 14:08:21 |
| Subject: Re: t_self as system column |
pgsql-committers by date
| Next: | From: Tom Lane | Date: 2010-07-06 14:42:16 |
| Subject: Re: Re: [COMMITTERS] pgsql: Fix log_temp_files docs and comments to say bytes not kilobytes. |
| Previous: | From: Tom Lane | Date: 2010-07-06 03:55:33 |
| Subject: pgsql: Still more third thoughts: when linking shared libraries, LDFLAGS |