On Thu, Jan 9, 2014, at 20:05, Magnus Hagander wrote:
> On Thu, Nov 14, 2013 at 10:27 AM, Mika Eloranta wrote:
>> On 13 Nov 2013, at 20:51, Mika Eloranta wrote:
>>
>>
>>
> Prevent excessive progress reporting that can grow to gigabytes
>>
> of outpu
On Thu, Jan 9, 2014, at 20:05, Magnus Hagander wrote:
> On Thu, Nov 14, 2013 at 10:27 AM, Mika Eloranta wrote:
>> On 13 Nov 2013, at 20:51, Mika Eloranta wrote:
>>
>>
>>
> Prevent excessive progress reporting that can grow to gigabytes
>>
> of outpu
xlogs have been generated.
Cheers,
--
Mika Eloranta
Ohmu Ltd. http://www.ohmu.fi/
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
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
Prevent excessive progress reporting that can grow to gigabytes
of output with large databases.
---
src/bin/pg_basebackup/pg_basebackup.c | 21 -
1 file changed, 12 insertions(+), 9 deletions(-)
diff --git a/src/bin/pg_basebackup/pg_basebackup.c
b/src/bin/pg_basebackup/pg_bas
On Nov 4, 2013, at 11:06, Heikki Linnakangas wrote:
> On 01.11.2013 11:42, Mika Eloranta wrote:
>> pg_receivexlog calculated the xlog segment number incorrectly
>> when started after the previous instance was interrupted.
>>
>> Resuming streaming only worked wh
pg_receivexlog calculated the xlog segment number incorrectly
when started after the previous instance was interrupted.
Resuming streaming only worked when the physical wal segment
counter was zero, i.e. for the first 256 segments or so.
---
src/bin/pg_basebackup/pg_receivexlog.c | 2 +-
1 file c
Hi all,
Here's a little SQL snippet that exposes an apparent regression in the 9.1.x
PL/Python behavior:
---clip---
# cat foo.sql
\set VERBOSITY 'verbose'
CREATE table bar (a INTEGER CONSTRAINT hello CHECK (a > 1));
CREATE OR REPLACE FUNCTION foo ()
RETURNS integer
AS $$
plpy.execute("INS
