Re: increasing the default WAL segment size

From: Robert Haas <robertmhaas(at)gmail(dot)com>
To: Michael Paquier <michael(dot)paquier(at)gmail(dot)com>
Cc: Beena Emerson <memissemerson(at)gmail(dot)com>, Jim Nasby <Jim(dot)Nasby(at)bluetreble(dot)com>, "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: increasing the default WAL segment size
Date: 2017-01-19 15:49:36
Views: Raw Message | Whole Thread | Download mbox
Lists: pgsql-hackers

On Wed, Jan 18, 2017 at 12:42 PM, Robert Haas <robertmhaas(at)gmail(dot)com> wrote:
> Problems 2-4 actually have to do with a DestReceiver of type
> DestRemote really, really wanting to have an associated Portal and
> database connection, so one approach is to create a stripped-down
> DestReceiver that doesn't care about those things and then passing
> that to GetPGVariable.

I tried that and it worked out pretty well, so I'm inclined to go with
this approach. Proposed patches attached. 0001 adds the new
DestReceiver type, and 0002 is a revised patch to implement the SHOW
command itself.

Thoughts, comments?

Robert Haas
The Enterprise PostgreSQL Company

Attachment Content-Type Size
0001-Add-new-DestReceiver-type-for-use-when-we-lack-catal.patch invalid/octet-stream 7.8 KB
0002-Add-a-SHOW-command-to-the-walsender-command-language.patch invalid/octet-stream 9.7 KB

In response to


Browse pgsql-hackers by date

  From Date Subject
Next Message Jorge Solórzano 2017-01-19 15:59:36 Re: [JDBC] SEGFAULT in HEAD with replication
Previous Message Albe Laurenz 2017-01-19 15:34:55 Re: ISO/IEC 9075-2:2016 for postgres community