Fix more user-visible elog() calls.
Michael Paquier discovered that this could be triggered via SQL;
give a nicer message instead.
Patch by Michael Paquier, reviewed by Masahiko Sawada.
Discussion:
http://postgr.es/m/cab7npqqtpg+lkktzdkn26judhcvpz0s1gnigzot4j8cyuuu...@mail.gmail.com
Branch
---
Fix more user-visible elog() calls.
Michael Paquier discovered that this could be triggered via SQL;
give a nicer message instead.
Patch by Michael Paquier, reviewed by Masahiko Sawada.
Discussion:
http://postgr.es/m/cab7npqqtpg+lkktzdkn26judhcvpz0s1gnigzot4j8cyuuu...@mail.gmail.com
Branch
---
Fix more user-visible elog() calls.
Michael Paquier discovered that this could be triggered via SQL;
give a nicer message instead.
Patch by Michael Paquier, reviewed by Masahiko Sawada.
Discussion:
http://postgr.es/m/cab7npqqtpg+lkktzdkn26judhcvpz0s1gnigzot4j8cyuuu...@mail.gmail.com
Branch
---
Fix more user-visible elog() calls.
Michael Paquier discovered that this could be triggered via SQL;
give a nicer message instead.
Patch by Michael Paquier, reviewed by Masahiko Sawada.
Discussion:
http://postgr.es/m/cab7npqqtpg+lkktzdkn26judhcvpz0s1gnigzot4j8cyuuu...@mail.gmail.com
Branch
---
Fix typo.
Etsuro Fujita
Discussion:
http://postgr.es/m/[email protected]
Branch
--
master
Details
---
https://git.postgresql.org/pg/commitdiff/4b2ba1fe0222b7820a2f4cd52b133baeb91c5a93
Modified Files
--
src/backend/catalog/partition.c | 2 +-
Improve comments in vacuum_rel() and analyze_rel().
Remove obsolete references to get_rel_oids(). Avoid listing specific
relkinds in the comments, since we seem unable to keep such things
in sync with the code, and it's not all that helpful anyhow.
Noted by Michael Paquier, though I rewrote the
Allow DML commands that create tables to use parallel query.
Haribabu Kommi, reviewed by Dilip Kumar and Rafia Sabih. Various
cosmetic changes by me to explain why this appears to be safe but
allowing inserts in parallel mode in general wouldn't be. Also, I
removed the REFRESH MATERIALIZED VIEW
On attach, consider skipping validation of subpartitions individually.
If the table attached as a partition is itself partitioned, individual
partitions might have constraints strong enough to skip scanning the
table even if the table actually attached does not. This is pretty
cheap to check, and
Improve error message when skipping scan of default partition.
It seems like a good idea to clearly distinguish between skipping the
scan of the new partition itself and skipping the scan of the default
partition.
Amit Langote
Discussion:
http://postgr.es/m/1f08b844-0078-aa8d-452e-7af3bf77d...@
On CREATE TABLE, consider skipping validation of subpartitions.
This is just like commit 14f67a8ee282ebc0de78e773fbd597f460ab4a54, but
for CREATE PARTITION rather than ATTACH PARTITION.
Jeevan Ladhe, with test case changes by me.
Discussion:
http://postgr.es/m/CAOgcT0MWwG8WBw8frFMtRYHAgDD=tpt6u
Fix typo in README.
s/BeginInternalSubtransaction/BeginInternalSubTransaction/
Branch
--
master
Details
---
https://git.postgresql.org/pg/commitdiff/fe9ba28ee852bb968bc8948d172c6bc0c70c50df
Modified Files
--
src/backend/access/transam/README | 4 ++--
1 file changed, 2 insert
Dave Page writes:
> On Mon, Oct 24, 2016 at 4:21 PM, Andrew Dunstan wrote:
>> On 10/24/2016 08:56 AM, Tom Lane wrote:
>>> I'd prefer the solution of disabling --with-openssl. If you just nuke
>>> those members, we never will find out whether the recent postgres_fdw
>>> changes pass on them. Bes
12 matches
Mail list logo
