On Wed, Aug 15, 2018 at 02:35:56PM -0300, Alvaro Herrera wrote:
> I had failed to push in the 9.4 branch. Done now.
Thanks Alvaro for working on the details. I would not have bothered
much myself as the set of columns was correct in 9.4, but for
consistency's sake that makes sense.
--
Michael
On 2018-Aug-03, Alvaro Herrera wrote:
> On 2018-Aug-03, Kyotaro HORIGUCHI wrote:
>
> > That said, I don't object to reduce the columns. Please find the
> > attached.
>
> Thanks, pushed.
I had failed to push in the 9.4 branch. Done now.
--
Álvaro Herrerahttps://www.2ndQuadrant
On Thu, Aug 09, 2018 at 03:58:09PM -0400, Alvaro Herrera wrote:
> Yeah. I suggest never changing subject lines, because Gmail has the
> nasty (mis-)feature of making such a response into a completely new
> thread. I don't know if Google paid mail service behaves in the same
> way.
If one uses Gm
On 2018-Aug-09, Kyotaro HORIGUCHI wrote:
> # I noticed that the subject has typo..
Yeah. I suggest never changing subject lines, because Gmail has the
nasty (mis-)feature of making such a response into a completely new
thread. I don't know if Google paid mail service behaves in the same
way.
S
At Sat, 4 Aug 2018 05:58:52 +0900, Michael Paquier wrote
in <20180803205852.gb20...@paquier.xyz>
> On Fri, Aug 03, 2018 at 04:37:05PM -0400, Alvaro Herrera wrote:
> > On 2018-Aug-03, Kyotaro HORIGUCHI wrote:
> >> That said, I don't object to reduce the columns. Please find the
> >> attached.
> >
On Fri, Aug 03, 2018 at 04:37:05PM -0400, Alvaro Herrera wrote:
> On 2018-Aug-03, Kyotaro HORIGUCHI wrote:
>> That said, I don't object to reduce the columns. Please find the
>> attached.
>
> Thanks, pushed.
Thanks Alvaro for keeping the three-column version, I was going to look
at the proposed
On 2018-Aug-03, Kyotaro HORIGUCHI wrote:
> That said, I don't object to reduce the columns. Please find the
> attached.
Thanks, pushed.
--
Álvaro Herrerahttps://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
At Fri, 3 Aug 2018 04:13:56 +0900, Michael Paquier wrote
in <20180802191356.gb2...@paquier.xyz>
> On Wed, Aug 01, 2018 at 01:04:37PM +0900, Kyotaro HORIGUCHI wrote:
> > The query and the result with four columns fit the current width.
>
> Just wondering, what is your reason behind the addition o
On Wed, Aug 01, 2018 at 01:04:37PM +0900, Kyotaro HORIGUCHI wrote:
> The query and the result with four columns fit the current width.
Just wondering, what is your reason behind the addition of restart_lsn?
This part of the documentation focuses on slot creation, so slot_name,
slot_type and active
At Wed, 1 Aug 2018 02:47:32 +0900, Michael Paquier wrote
in <20180731174732.gd2...@paquier.xyz>
> On Tue, Jul 31, 2018 at 10:59:14AM -0400, Alvaro Herrera wrote:
> > How about pasting it like this?
> >
> > alvherre=# select * from pg_replication_slots \gx
> > ─[ RECORD 1 ]───┬
>
On Tue, Jul 31, 2018 at 10:59:14AM -0400, Alvaro Herrera wrote:
> How about pasting it like this?
>
> alvherre=# select * from pg_replication_slots \gx
> ─[ RECORD 1 ]───┬
> slot_name │ node_a_slot
> plugin │
> slot_type │ physical
> datoid
On 2018-Jul-31, Kyotaro HORIGUCHI wrote:
> But, just fixing it makes the line seemingly a bit too long..
How about pasting it like this?
alvherre=# select * from pg_replication_slots \gx
─[ RECORD 1 ]───┬
slot_name │ node_a_slot
plugin │
slot_type
Hello.
I found that an example output in the following page is not
correct for the version.
https://www.postgresql.org/docs/10/static/warm-standby.html
postgres=# SELECT * FROM pg_replication_slots;
> slot_name | slot_type | datoid | database | active | xmin | restart_lsn |
> confirmed_flush
13 matches
Mail list logo
