pgsql: Use whitelist to choose files scanned with pg_verify_checksums

2018-10-19 Thread Michael Paquier
Use whitelist to choose files scanned with pg_verify_checksums The original implementation of pg_verify_checksums used a blacklist to decide which files should be skipped for scanning as they do not include data checksums, like pg_internal.init or pg_control. However, this missed two things: - So

pgsql: Use whitelist to choose files scanned with pg_verify_checksums

2018-10-19 Thread Michael Paquier
Use whitelist to choose files scanned with pg_verify_checksums The original implementation of pg_verify_checksums used a blacklist to decide which files should be skipped for scanning as they do not include data checksums, like pg_internal.init or pg_control. However, this missed two things: - So

pgsql: Silence perlcritic warning about missing return.

2018-10-19 Thread Tom Lane
Silence perlcritic warning about missing return. Per buildfarm member crake. Branch -- master Details --- https://git.postgresql.org/pg/commitdiff/e65e8f8218e3b99534f01bd5e67b1e6ec99e6f7e Modified Files -- src/bin/pg_verify_checksums/t/002_actions.pl | 2 ++ 1 file changed, 2

pgsql: Update time zone data files to tzdata release 2018f.

2018-10-19 Thread Tom Lane
Update time zone data files to tzdata release 2018f. DST law changes in Chile, Fiji, and Russia (Volgograd). Historical corrections for China, Japan, Macau, and North Korea. Note: like the previous tzdata update, this involves a depressingly large amount of semantically-meaningless churn in tzdat

pgsql: Update time zone data files to tzdata release 2018f.

2018-10-19 Thread Tom Lane
Update time zone data files to tzdata release 2018f. DST law changes in Chile, Fiji, and Russia (Volgograd). Historical corrections for China, Japan, Macau, and North Korea. Note: like the previous tzdata update, this involves a depressingly large amount of semantically-meaningless churn in tzdat

pgsql: Update time zone data files to tzdata release 2018f.

2018-10-19 Thread Tom Lane
Update time zone data files to tzdata release 2018f. DST law changes in Chile, Fiji, and Russia (Volgograd). Historical corrections for China, Japan, Macau, and North Korea. Note: like the previous tzdata update, this involves a depressingly large amount of semantically-meaningless churn in tzdat

pgsql: Update time zone data files to tzdata release 2018f.

2018-10-19 Thread Tom Lane
Update time zone data files to tzdata release 2018f. DST law changes in Chile, Fiji, and Russia (Volgograd). Historical corrections for China, Japan, Macau, and North Korea. Note: like the previous tzdata update, this involves a depressingly large amount of semantically-meaningless churn in tzdat

pgsql: Update time zone data files to tzdata release 2018f.

2018-10-19 Thread Tom Lane
Update time zone data files to tzdata release 2018f. DST law changes in Chile, Fiji, and Russia (Volgograd). Historical corrections for China, Japan, Macau, and North Korea. Note: like the previous tzdata update, this involves a depressingly large amount of semantically-meaningless churn in tzdat

pgsql: Update time zone data files to tzdata release 2018f.

2018-10-19 Thread Tom Lane
Update time zone data files to tzdata release 2018f. DST law changes in Chile, Fiji, and Russia (Volgograd). Historical corrections for China, Japan, Macau, and North Korea. Note: like the previous tzdata update, this involves a depressingly large amount of semantically-meaningless churn in tzdat

pgsql: Update time zone data files to tzdata release 2018f.

2018-10-19 Thread Tom Lane
Update time zone data files to tzdata release 2018f. DST law changes in Chile, Fiji, and Russia (Volgograd). Historical corrections for China, Japan, Macau, and North Korea. Note: like the previous tzdata update, this involves a depressingly large amount of semantically-meaningless churn in tzdat

pgsql: Sync our copy of the timezone library with IANA release tzcode20

2018-10-19 Thread Tom Lane
Sync our copy of the timezone library with IANA release tzcode2018f. About half of this is purely cosmetic changes to reduce the diff between our code and theirs, like inserting "const" markers where they have them. The other half is tracking actual code changes in zic.c and localtime.c. I don't

pgsql: Sync our copy of the timezone library with IANA release tzcode20

2018-10-19 Thread Tom Lane
Sync our copy of the timezone library with IANA release tzcode2018f. About half of this is purely cosmetic changes to reduce the diff between our code and theirs, like inserting "const" markers where they have them. The other half is tracking actual code changes in zic.c and localtime.c. I don't

pgsql: Sync our copy of the timezone library with IANA release tzcode20

2018-10-19 Thread Tom Lane
Sync our copy of the timezone library with IANA release tzcode2018f. About half of this is purely cosmetic changes to reduce the diff between our code and theirs, like inserting "const" markers where they have them. The other half is tracking actual code changes in zic.c and localtime.c. I don't

pgsql: Sync our copy of the timezone library with IANA release tzcode20

2018-10-19 Thread Tom Lane
Sync our copy of the timezone library with IANA release tzcode2018f. About half of this is purely cosmetic changes to reduce the diff between our code and theirs, like inserting "const" markers where they have them. The other half is tracking actual code changes in zic.c and localtime.c. I don't

pgsql: Sync our copy of the timezone library with IANA release tzcode20

2018-10-19 Thread Tom Lane
Sync our copy of the timezone library with IANA release tzcode2018f. About half of this is purely cosmetic changes to reduce the diff between our code and theirs, like inserting "const" markers where they have them. The other half is tracking actual code changes in zic.c and localtime.c. I don't

pgsql: Sync our copy of the timezone library with IANA release tzcode20

2018-10-19 Thread Tom Lane
Sync our copy of the timezone library with IANA release tzcode2018f. About half of this is purely cosmetic changes to reduce the diff between our code and theirs, like inserting "const" markers where they have them. The other half is tracking actual code changes in zic.c and localtime.c. I don't

pgsql: Sync our copy of the timezone library with IANA release tzcode20

2018-10-19 Thread Tom Lane
Sync our copy of the timezone library with IANA release tzcode2018f. About half of this is purely cosmetic changes to reduce the diff between our code and theirs, like inserting "const" markers where they have them. The other half is tracking actual code changes in zic.c and localtime.c. I don't

pgsql: Server-side fix for delayed NOTIFY and SIGTERM processing.

2018-10-19 Thread Tom Lane
Server-side fix for delayed NOTIFY and SIGTERM processing. Commit 4f85fde8e introduced some code that was meant to ensure that we'd process cancel, die, sinval catchup, and notify interrupts while waiting for client input. But there was a flaw: it supposed that the process latch would be set upon

pgsql: Client-side fixes for delayed NOTIFY receipt.

2018-10-19 Thread Tom Lane
Client-side fixes for delayed NOTIFY receipt. PQnotifies() is defined to just process already-read data, not try to read any more from the socket. (This is a debatable decision, perhaps, but I'm hesitant to change longstanding library behavior.) The documentation has long recommended calling PQc

pgsql: Server-side fix for delayed NOTIFY and SIGTERM processing.

2018-10-19 Thread Tom Lane
Server-side fix for delayed NOTIFY and SIGTERM processing. Commit 4f85fde8e introduced some code that was meant to ensure that we'd process cancel, die, sinval catchup, and notify interrupts while waiting for client input. But there was a flaw: it supposed that the process latch would be set upon

pgsql: Client-side fixes for delayed NOTIFY receipt.

2018-10-19 Thread Tom Lane
Client-side fixes for delayed NOTIFY receipt. PQnotifies() is defined to just process already-read data, not try to read any more from the socket. (This is a debatable decision, perhaps, but I'm hesitant to change longstanding library behavior.) The documentation has long recommended calling PQc

pgsql: Server-side fix for delayed NOTIFY and SIGTERM processing.

2018-10-19 Thread Tom Lane
Server-side fix for delayed NOTIFY and SIGTERM processing. Commit 4f85fde8e introduced some code that was meant to ensure that we'd process cancel, die, sinval catchup, and notify interrupts while waiting for client input. But there was a flaw: it supposed that the process latch would be set upon

pgsql: Server-side fix for delayed NOTIFY and SIGTERM processing.

2018-10-19 Thread Tom Lane
Server-side fix for delayed NOTIFY and SIGTERM processing. Commit 4f85fde8e introduced some code that was meant to ensure that we'd process cancel, die, sinval catchup, and notify interrupts while waiting for client input. But there was a flaw: it supposed that the process latch would be set upon

pgsql: Server-side fix for delayed NOTIFY and SIGTERM processing.

2018-10-19 Thread Tom Lane
Server-side fix for delayed NOTIFY and SIGTERM processing. Commit 4f85fde8e introduced some code that was meant to ensure that we'd process cancel, die, sinval catchup, and notify interrupts while waiting for client input. But there was a flaw: it supposed that the process latch would be set upon

pgsql: Client-side fixes for delayed NOTIFY receipt.

2018-10-19 Thread Tom Lane
Client-side fixes for delayed NOTIFY receipt. PQnotifies() is defined to just process already-read data, not try to read any more from the socket. (This is a debatable decision, perhaps, but I'm hesitant to change longstanding library behavior.) The documentation has long recommended calling PQc

pgsql: Client-side fixes for delayed NOTIFY receipt.

2018-10-19 Thread Tom Lane
Client-side fixes for delayed NOTIFY receipt. PQnotifies() is defined to just process already-read data, not try to read any more from the socket. (This is a debatable decision, perhaps, but I'm hesitant to change longstanding library behavior.) The documentation has long recommended calling PQc

pgsql: Client-side fixes for delayed NOTIFY receipt.

2018-10-19 Thread Tom Lane
Client-side fixes for delayed NOTIFY receipt. PQnotifies() is defined to just process already-read data, not try to read any more from the socket. (This is a debatable decision, perhaps, but I'm hesitant to change longstanding library behavior.) The documentation has long recommended calling PQc

Re: pgsql: Silence perlcritic warning about missing return.

2018-10-19 Thread Michael Paquier
On Fri, Oct 19, 2018 at 06:00:26PM +, Tom Lane wrote: > Silence perlcritic warning about missing return. > > Per buildfarm member crake. Thanks! I did not know that this was run automatically. -- Michael signature.asc Description: PGP signature