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

Re: [COMMITTERS] pgsql: Revert "commit_delay" change; just add comment that we don't hav

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: pgsql-hackers(at)postgresql(dot)org, Peter Geoghegan <peter(at)2ndquadrant(dot)com>
Cc: Bruce Momjian <bruce(at)momjian(dot)us>
Subject: Re: [COMMITTERS] pgsql: Revert "commit_delay" change; just add comment that we don't hav
Date: 2012-08-15 13:39:38
Message-ID: 2221.1345037978@sss.pgh.pa.us (view raw or flat)
Thread:
Lists: pgsql-committerspgsql-hackers
Peter Geoghegan <peter(at)2ndquadrant(dot)com> writes:
> Why does commit_delay have to be an integer? Can't we devise a way of
> manipulating it in units of milliseconds, but have the internal
> representation be a double, as with pg_stat_statements' total_time
> column?

If you wanted to re-implement all the guc.c logic for supporting
unit-ified values such that it would also work with floats, we could
do that.  It seems like way more mechanism than the problem is worth
however.

			regards, tom lane


In response to

Responses

pgsql-hackers by date

Next:From: Tom LaneDate: 2012-08-15 13:48:43
Subject: Re: sha1, sha2 functions into core?
Previous:From: Marko KreenDate: 2012-08-15 11:42:13
Subject: Re: sha1, sha2 functions into core?

pgsql-committers by date

Next:From: Bruce MomjianDate: 2012-08-15 15:23:17
Subject: pgsql: Properly escape usernames in initdb,so names with single-quotes
Previous:From: Peter GeogheganDate: 2012-08-15 10:51:54
Subject: Re: [COMMITTERS] pgsql: Revert "commit_delay" change; just add comment that we don't hav

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