Re: [COMMITTERS] pgsql: Reindent table partitioning code.

From: Robert Haas <robertmhaas(at)gmail(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: [COMMITTERS] pgsql: Reindent table partitioning code.
Date: 2017-01-24 15:51:58
Message-ID: CA+TgmoYu6FnFM-ic3aRhi+1755638_U64mKsbmtBuAuOC8Przg@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-committers pgsql-hackers

On Tue, Jan 24, 2017 at 10:28 AM, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> Robert Haas <rhaas(at)postgresql(dot)org> writes:
>> Reindent table partitioning code.
>
> Oh, thank you, I was starting to get annoyed with that too.

Glad you like. The pgindent damage introduced by the logical
replication commits is even more extensive, but I didn't want to touch
that without discussion. Peter might want to look for a time when not
too many patches are pending to do something similar, though.

--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company

In response to

Responses

Browse pgsql-committers by date

  From Date Subject
Next Message Robert Haas 2017-01-24 20:44:34 pgsql: Set ecxt_scantuple correctly for tuple routing.
Previous Message Tom Lane 2017-01-24 15:28:38 Re: pgsql: Reindent table partitioning code.

Browse pgsql-hackers by date

  From Date Subject
Next Message Robert Haas 2017-01-24 16:25:36 Re: [ patch ] pg_dump: new --custom-fetch-table and --custom-fetch-value parameters
Previous Message Robert Haas 2017-01-24 15:49:57 Re: [PATCH] Transaction traceability - txid_status(bigint)