pg.ddx.io  pgsql-hackers@postgresql.org mailing list archive  

help / color / mirror / Atom feed
From: Tom Lane <tgl@sss.pgh.pa.us>
To: Robert Haas <robertmhaas@gmail.com>
Cc: Marina Polyakova <m.polyakova@postgrespro.ru>
Cc: Victor Wagner *EXTERN* <vitus@wagner.pp.ru>
Cc: Andres Freund <andres@anarazel.de>
Cc: pgsql-hackers@postgresql.org <pgsql-hackers@postgresql.org>
Cc: Alvaro Herrera <alvherre@alvh.no-ip.org>
Subject: Re: master make check fails on Solaris 10
Date: Thu, 18 Jan 2018 13:28:16 -0500
Message-ID: <10980.1516300096@sss.pgh.pa.us> (raw)
In-Reply-To: <CA+TgmoZa-_OBtVWK5brHCqJABPd7zsCxV9Huh+V=hAUTAik=zg@mail.gmail.com>
References: <0d3a9fa264cebe1cb9966f37b7c06e86@postgrespro.ru>
	<20180111173938.jimybeayp2u5mmup@alap3.anarazel.de>
	<31a342fa6a025a8bdfc5b8b19c29d56d@postgrespro.ru>
	<fc3c1b52d2d4121cccfc13635005bbd0@postgrespro.ru>
	<1232.1515780057@sss.pgh.pa.us>
	<b946893927ccfd87146d8a7c9f3bbe29@postgrespro.ru>
	<15299.1515867055@sss.pgh.pa.us>
	<a5559105243efcf6fb619d86c5702115@postgrespro.ru>
	<18209.1516059711@sss.pgh.pa.us>
	<90ab676392c8f9c84431976147097cf0@postgrespro.ru>
	<17897.1516202926@sss.pgh.pa.us>
	<1c70bab595a37ffa3a7fafea29fa6f55@postgrespro.ru>
	<31743.1516206789@sss.pgh.pa.us>
	<0e183c12a68af526ebc03c5c26206c44@postgrespro.ru>
	<16822.1516287408@sss.pgh.pa.us>
	<c737e36bb5eee1fa1c0f24dc33ba9e2e@postgrespro.ru>
	<5487.1516294381@sss.pgh.pa.us>
	<99cd20828c6c38c22ff8a08cbd294982@postgrespro.ru>
	<7326.1516296284@sss.pgh.pa.us>
	<CA+TgmoZzCCQ36trRHez2ZA6rbHb_J5P1A05MK_ry4rPGxmyW=w@mail.gmail.com>
	<9189.1516298580@sss.pgh.pa.us>
	<CA+TgmoZa-_OBtVWK5brHCqJABPd7zsCxV9Huh+V=hAUTAik=zg@mail.gmail! .com>

Robert Haas <robertmhaas@gmail.com> writes:
> Anyway, that's really an academic debate.  My real point is: I do not
> think we should reject out of hand the idea that a patch introducing
> some new notation to deal with this might be acceptable.  I am not
> volunteering to write such a patch, and anyone who tries should be
> aware that there is a chance that it will be rejected on grounds of
> ugliness.  However, if they decide to try anyway, we should read the
> patch and see how ugly it really is.  Maybe it's not that bad.

Sure.  I'm not intending to write such a patch either.

			regards, tom lane




view thread (46+ messages)  latest in thread

Message-ID: <10980.1516300096@sss.pgh.pa.us>
Permalink:  ../10980.1516300096@sss.pgh.pa.us/
Also on:    postgresql.org/message-id/10980.1516300096@sss.pgh.pa.us

 · 

reply
Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: pgsql-hackers@postgresql.org
  Cc: tgl@sss.pgh.pa.us, robertmhaas@gmail.com, m.polyakova@postgrespro.ru, vitus@wagner.pp.ru, andres@anarazel.de, alvherre@alvh.no-ip.org
  Subject: Re: master make check fails on Solaris 10
  In-Reply-To: <10980.1516300096@sss.pgh.pa.us>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox