Re: [HACKERS] [PATCH] pg_basebackup: progress report max once per second

2013-11-14 Thread Mika Eloranta
On 13 Nov 2013, at 20:51, Mika Eloranta wrote: > Prevent excessive progress reporting that can grow to gigabytes > of output with large databases. Same patch as an attachment. -- Mika Eloranta Ohmu Ltd. http://www.ohmu.fi/ 0001-pg_basebackup-progress-report-max-once-per-second.patch Descri

Re: [HACKERS] appendPQExpBufferVA vs appendStringInfoVA

2013-11-14 Thread David Rowley
On Sun, Nov 3, 2013 at 3:18 AM, David Rowley wrote: > > I'm low on ideas on how to improve things much around here for now, but > for what it's worth, I did create a patch which changes unnecessary calls > to appendPQExpBuffer() into calls to appendPQExpBufferStr() similar to the > recent one for

Re: [HACKERS] nested hstore patch

2013-11-14 Thread Hannu Krosing
On 11/14/2013 01:32 AM, David E. Wheeler wrote: > On Nov 13, 2013, at 3:59 PM, Hannu Krosing wrote: > >> I remember strong voices in support of *not* normalising json, so that >> things like >> >> {"a":1,"a":true, "a":"b", "a":none} >> >> would go through the system unaltered, for claimed standard

[HACKERS] Storing pg_stat_statements query texts externally, pg_stat_statements in core

2013-11-14 Thread Peter Geoghegan
Attached patch allows pg_stat_statements to store arbitrarily long query texts, using an external, transparently managed lookaside file. This is of great practical benefit to certain types of users, who need to understand the execution costs of queries with associated excessively long query texts,

<    1   2