Allow parallel DISTINCT
We've supported parallel aggregation since e06a38965. At the time, we
didn't quite get around to also adding parallel DISTINCT. So, let's do
that now.
This is implemented by introducing a two-phase DISTINCT. Phase 1 is
performed on parallel workers, rows are made distinc
Fix broken regression test caused by 22c4e88eb
Per buildfarm members hoverfly and thorntail
Branch
--
master
Details
---
https://git.postgresql.org/pg/commitdiff/945f395aeb74cea77d5239db01357bbcbea80534
Modified Files
--
src/test/regress/expected/select_distinct.out | 2 ++
s
psql: Improve portability of query cancel test
Some shells apparently don't support $PPID, so skip the test in that
case.
Branch
--
master
Details
---
https://git.postgresql.org/pg/commitdiff/c818c25f448d0085e1bb2be402463a4b28bc20c4
Modified Files
--
src/bin/psql/t/020_cance
I see that c818c25f4 worked around sidewinder's issue with
this test, but wrasse is still unhappy. I was able to
duplicate the problem on wrasse's host, so I ran it under
truss to see if I could see what's happening.
What the truss log shows is that the Perl script successfully
reads psql.pid and
Fix backup manifests to generate correct WAL-Ranges across timelines
In a backup manifest, WAL-Ranges stores the range of WAL that is
required for the backup to be valid. pg_verifybackup would then
internally use pg_waldump for the checks based on this data.
When the timeline where the backup st
Fix backup manifests to generate correct WAL-Ranges across timelines
In a backup manifest, WAL-Ranges stores the range of WAL that is
required for the backup to be valid. pg_verifybackup would then
internally use pg_waldump for the checks based on this data.
When the timeline where the backup st
Fix backup manifests to generate correct WAL-Ranges across timelines
In a backup manifest, WAL-Ranges stores the range of WAL that is
required for the backup to be valid. pg_verifybackup would then
internally use pg_waldump for the checks based on this data.
When the timeline where the backup st
