Postgres Pro
Downloads
Home   >   mailing lists

Re: why pg_size_pretty is volatile? - Mailing list pgsql-hackers

From Michael Paquier
Subject Re: why pg_size_pretty is volatile?
Date
Msg-id CAB7nPqRgNH85o4wqSx826ojynvVaLBWyQKxpiQALhMEQZQwTKw@mail.gmail.com
Whole thread Raw
In response to why pg_size_pretty is volatile?  (Pavel Stehule <pavel.stehule@gmail.com>)
Responses Re: why pg_size_pretty is volatile?  (Pavel Stehule <pavel.stehule@gmail.com>)
List pgsql-hackers
Tree view 
On Tue, Jan 26, 2016 at 5:35 AM, Pavel Stehule <pavel.stehule@gmail.com> wrote:
> Vitaly Burovoy pointed on bug in my patch - a pg_size_bytes was VOLATILE
> function. It is copy/paste bug - I used pg_size_pretty definition, so the
> question is: why pg_size_pretty is volatile? It should be immutable too.

+1. This function relies only on the input of its argument to generate a result.
-- 
Michael

pgsql-hackers by date:

Previous
From: Amit Langote
Date:
Subject: Re: [PROPOSAL] VACUUM Progress Checker.
Next
From: Kouhei Kaigai
Date:
Subject: Re: CustomScan in a larger structure (RE: CustomScan support on readfuncs.c)