Skip site navigation (1) Skip section navigation (2)

== PostgreSQL Weekly News - February 04 2018 ==

From: David Fetter <david(at)fetter(dot)org>
To: PostgreSQL Announce <pgsql-announce(at)postgresql(dot)org>
Subject: == PostgreSQL Weekly News - February 04 2018 ==
Date: 2018-02-04 21:54:24
Message-ID: 20180204215424.GA4423@fetter.org (view raw, whole thread or download thread mbox)
Thread:
Lists: pgsql-announce
== PostgreSQL Weekly News - February 04 2018 ==

== PostgreSQL Product News ==

pgsodium 1.0.16, an extention which adds libsodium encryption to PostgreSQL,
released.
https://github.com/michelp/pgsodium

== PostgreSQL Jobs for February ==

http://archives.postgresql.org/pgsql-jobs/2018-02/

== PostgreSQL Local ==

Prague PostgreSQL Developer Day 2018 (P2D2 2018) is a two-day
conference that will be held on February 14-15 2018 in Prague, Czech Republic.
http://www.p2d2.cz/

PGConf India 2018 will be on February 22-23, 2018 in Bengaluru, Karnataka.
http://pgconf.in/

PostgreSQL(at)SCaLE is a two day, two track event which takes place on
March 8-9, 2018, at Pasadena Convention Center, as part of SCaLE 16X.
http://www.socallinuxexpo.org/scale/16x/cfp

Nordic PGDay 2018 will be held in Oslo, Norway, at the Radisson Blu Hotel
Nydalen, on March 13, 2018. Registration is open and schedule is posted
https://2018.nordicpgday.org/

pgDay Paris 2018 will be held in Paris, France at the Espace Saint-Martin, on
March 15 2018. Registration is open.
http://2018.pgday.paris/

PGConf APAC 2018 will be held in Singapore March 22-23, 2018.
http://2018.pgconfapac.org/

The German-speaking PostgreSQL Conference 2018 will take place on April 13th,
2018 in Berlin.
http://2018.pgconf.de/

PGConfNepal 2018 will be held May 4-5, 2018 at Kathmandu University, Dhulikhel,
Nepal.
https://postgresconf.org/conferences/Nepal2018/program/proposals
https://postgresconf.org/conferences/Nepal2018

PGCon 2018 will take place in Ottawa on May 29 - June 1, 2018.
https://www.pgcon.org/2018/

PGConf.Brazil 2018 will take place in São Paulo, Brazil on August 3-4 2018. The
CfP will open soon.
http://pgconf.com.br

== PostgreSQL in the News ==

Planet PostgreSQL: http://planet.postgresql.org/

PostgreSQL Weekly News is brought to you this week by David Fetter

Submit news and announcements by Sunday at 3:00pm EST5EDT.  Please send English
language ones to david(at)fetter(dot)org, German language to pwn(at)pgug(dot)de, Italian
language to pwn(at)itpug(dot)org(dot)

== Applied Patches ==

Tom Lane pushed:

- Avoid misleading psql password prompt when username is multiply specified.
  When a password is needed, cases such as psql -d
  "postgresql://alice(at)localhost/testdb" -U bob would incorrectly prompt for
  "Password for user bob: ", when actually the connection will be attempted with
  username alice.  The priority order of which name to use isn't that important
  here, but the misleading prompt is.  When we are prompting for a password
  after initial connection failure, we can fix this reliably by looking at
  PQuser(conn) to see how libpq interpreted the connection arguments.  But when
  we're doing a forced password prompt because of a -W switch, we can't use that
  solution.  Fortunately, because the main use of -W is for noninteractive
  situations, it's less critical to produce a helpful prompt in such cases.  I
  made the startup prompt for -W just say "Password: " all the time, rather than
  expending extra code on trying to identify which username to use.  In the case
  of a \c command (after -W has been given), there's already logic in do_connect
  that determines whether the "dbname" is a connstring or URI, so we can avoid
  lobotomizing the prompt except in cases that are actually dubious.  (We could
  do similarly in startup.c if anyone complains, but for now it seems not
  worthwhile, especially since that would still be only a partial solution.) Per
  bug #15025 from Akos Vandra.  Although this is arguably a bug fix, it doesn't
  seem worth back-patching.  The case where it matters seems like a very
  corner-case usage, and someone might complain that we'd changed the behavior
  of -W in a minor release.  Discussion:
  https://postgr.es/m/20180123130013.7407.24749@wrigleys.postgresql.org
  https://git.postgresql.org/pg/commitdiff/15be27460191a9ffb149cc98f6fbf97c369a6b1e

- Save a few bytes by removing useless last argument to SearchCatCacheList.
  There's never any value in giving a fully specified cache key to
  SearchCatCacheList: you might as well call SearchCatCache instead, since there
  could be only one match.  So the maximum useful number of key arguments is one
  less than the supported number of key columns.  We might as well remove the
  useless extra argument and save some few bytes per call site, as well as a
  cycle or so per call.  I believe the reason it was coded like this is that
  originally, callers had to write out all the dummy arguments in each call, and
  so it seemed less confusing if SearchCatCache and SearchCatCacheList took the
  same number of key arguments.  But since commit e26c539e9, callers only write
  their live arguments explicitly, making that a non-factor; and there's surely
  been enough time for third-party modules to adapt to that coding style.  So
  this is only an ABI break not an API break for callers.  Per discussion with
  Oliver Ford, this might also make it less confusing how to use
  SearchCatCacheList correctly.  Discussion:
  https://postgr.es/m/27788.1517069693@sss.pgh.pa.us
  https://git.postgresql.org/pg/commitdiff/97d4445a033f1cc02784d42561b52b3441c8eddd

- First-draft release notes for 10.2.  As usual, the release notes for other
  branches will be made by cutting these down, but put them up for community
  review first.
  https://git.postgresql.org/pg/commitdiff/bf641d3376018c40860f26167a60febff5bc1f51

- Be more wary about shm_toc_lookup failure.  Commit 445dbd82a basically missed
  the point of commit d46633506, which was that we shouldn't allow
  shm_toc_lookup() failure to lead to a core dump or assertion crash, because
  the odds of such a failure should never be considered negligible.  It's
  correct that we can't expect the PARALLEL_KEY_ERROR_QUEUE TOC entry to be
  there if we have no workers.  But if we have no workers, we're not going to do
  anything in this function with the lookup result anyway, so let's just skip
  it.  That lets the code use the easy-to-prove-safe noError=false case, rather
  than anything requiring effort to review.  Back-patch to v10, like the
  previous commit.  Discussion:
  https://postgr.es/m/3647.1517601675@sss.pgh.pa.us
  https://git.postgresql.org/pg/commitdiff/957ff087c822c95f63df956e1a91c15614ecb2b4

- Fix another instance of unsafe coding for shm_toc_lookup failure.  One or
  another author of commit 5bcf389ec seems to have thought that computing an
  offset from a NULL pointer would yield another NULL pointer.  There may
  possibly be architectures where that works, but common machines don't work
  like that.  Per a quick code review of places calling shm_toc_lookup and not
  using noError = false.
  https://git.postgresql.org/pg/commitdiff/d59ff4ab3111f20054425d82dab1393101dcfe8e

- Minor copy-editing for 10.2 release notes.  Second pass after taking a break
  ...
  https://git.postgresql.org/pg/commitdiff/794eb3a8f00519fac561831dee35f4ee557bd08b

- Doc: minor clarifications in xindex.sgml.  I noticed some slightly confusing
  or out-of-date verbiage here while working on the window RANGE patch.  Seems
  worth committing separately.
  https://git.postgresql.org/pg/commitdiff/64fb645914741ffc3aee646308416c209c6ff06b

- Release notes for 10.2, 9.6.7, 9.5.11, 9.4.16, 9.3.21.
  https://git.postgresql.org/pg/commitdiff/cf1cba3110f339eddecd66cdf7d8f9b4370f34c2

Andres Freund pushed:

- Improve bit perturbation in TupleHashTableHash.  The changes in
  b81b5a96f424531b97cdd1dba97d9d1b9c9d372e did not fully address the issue,
  because the bit-mixing of the IV into the final hash-key didn't prevent
  clustering in the input-data survive in the output data.  This didn't cause a
  lot of problems because of the additional growth conditions added
  d4c62a6b623d6eef88218158e9fa3cf974c6c7e5. But as we want to rein those in due
  to explosive growth in some edges, this needs to be fixed.  Author: Andres
  Freund Discussion:
  https://postgr.es/m/20171127185700.1470.20362@wrigleys.postgresql.org
  Backpatch: 10, where simplehash was introduced
  https://git.postgresql.org/pg/commitdiff/c068f87723ca9cded1f2aceb956ede49de651690

- Prevent growth of simplehash tables when they're "too empty".  In cases where
  simplehash tables where filled with either a lot of conflicting hash-values,
  or values that hash to consecutive values (i.e. build "chains") the growth
  heuristics in d4c62a6b623d6eef88218158e9fa3cf974c6c7e5 could trigger rather
  explosively.  To fix that, address some of the reasons (see previous commit)
  of why the growth heuristics where needed, and only allow growth when the
  table isn't too empty. While that means there's a few cases of bad input that
  can be slower, that seems a lot better than running very quickly out of
  memory.  Author: Tomas Vondra and Andres Freund, with additional input by
  Thomas Munro, Tom Lane Todd A. Cook Reported-By: Todd A. Cook, Tomas Vondra,
  Thomas Munro Discussion:
  https://postgr.es/m/20171127185700.1470.20362@wrigleys.postgresql.org
  Backpatch: 10, where simplehash was introduced
  https://git.postgresql.org/pg/commitdiff/ab9f2c429d8fbd3580cd2ae5f2054ba6956b1f60

- Introduce ExecQualAndReset() helper.  It's a common task to evaluate a qual
  and reset the corresponding expression context. Currently that requires
  storing the result of the qual eval, resetting the context, and then reacting
  on the result. As that's awkward several places only reset the context next
  time through a node. That's not great, so introduce a helper that evaluates
  and resets.  It's a bit ugly that it currently uses MemoryContextReset()
  instead of ResetExprContext(), but that seems easier than reordering all of
  executor.h.  Author: Andres Freund Discussion:
  https://postgr.es/m/20180109222544.f7loxrunqh3xjl5f@alap3.anarazel.de
  https://git.postgresql.org/pg/commitdiff/c12693d8f3bbbffcb79f6af476cc647402e1145e

- Initialize unused ExprEvalStep fields.  ExecPushExprSlots didn't initialize
  ExprEvalStep's resvalue/resnull steps as it didn't use them. That caused wrong
  valgrind warnings for an upcoming patch, so zero-intialize.  Also
  zero-initialize all scratch ExprEvalStep's allocated on the stack, to avoid
  issues with similar future omissions of non-critial data.
  https://git.postgresql.org/pg/commitdiff/fc96c6942551dafa6cb2a6000cbc9b20643e5db3

Peter Eisentraut pushed:

- doc: Clarify pg_upgrade documentation.  Clarify that the restriction against
  reg* types only applies to table columns using these types, not to the type
  appearing in any other way, for example as a function argument.
  https://git.postgresql.org/pg/commitdiff/1e1e599d6663c4a65388b40f84b2ea6b7c6e381b

- Silence complaint about dead assignment.  The preferred place for "placate
  compiler" assignments is after elog(ERROR), not before it.  Otherwise,
  scan-build complains about a dead assignment.
  https://git.postgresql.org/pg/commitdiff/07e524d3e955a79b94918d076642b3ac8e84b65f

- Add some noreturn attributes to help static analyzers.
  https://git.postgresql.org/pg/commitdiff/a044378ce2f6268a996c8cce2b7bfb5d82b05c90

- Remove dead assignment.  per scan-build
  https://git.postgresql.org/pg/commitdiff/6ad3611e1ea6fef6ac0c746d1565b3f6a856b593

- Fix up references to scram-sha-256.  pg_hba_file_rules erroneously reported
  this as scram-sha256.  Fix that.  To avoid future errors and confusion, also
  adjust documentation links and internal symbols to have a separator between
  "sha" and "256".  Reported-by: Christophe Courtois
  <christophe(dot)courtois(at)dalibo(dot)com> Author: Michael Paquier
  <michael(dot)paquier(at)gmail(dot)com>
  https://git.postgresql.org/pg/commitdiff/38d485fdaa5739627b642303cc172acc1487b90a

- Refactor client-side SSL certificate checking code.  Separate the parts
  specific to the SSL library from the general logic.  The previous code
  structure was open_client_SSL() calls verify_peer_name_matches_certificate()
  calls verify_peer_name_matches_certificate_name() calls
  wildcard_certificate_match() and was completely in fe-secure-openssl.c.  The
  new structure is open_client_SSL() [openssl] calls
  pq_verify_peer_name_matches_certificate() [generic] calls
  pgtls_verify_peer_name_matches_certificate_guts() [openssl] calls
  openssl_verify_peer_name_matches_certificate_name() [openssl] calls
  pq_verify_peer_name_matches_certificate_name() [generic] calls
  wildcard_certificate_match() [generic] Move the generic functions into a new
  file fe-secure-common.c, so the calls generally go fe-connect.c -> fe-secure.c
  -> fe-secure-${impl}.c -> fe-secure-common.c, although there is a bit of
  back-and-forth between the last two.  Reviewed-by: Michael Paquier
  <michael(dot)paquier(at)gmail(dot)com>
  https://git.postgresql.org/pg/commitdiff/f75a95915528646cbfaf238fb48b3ffa17969383

- Fix application of identity values in some cases.  Investigation of
  2d2d06b7e27e3177d5bef0061801c75946871db3 revealed that identity values were
  not applied in some further cases, including logical replication subscribers,
  VALUES RTEs, and ALTER TABLE ... ADD COLUMN.  To fix all that, apply the
  identity column expression in build_column_default() instead of repeating the
  same logic at each call site.  For ALTER TABLE ... ADD COLUMN ... IDENTITY,
  the previous coding completely ignored that existing rows for the new column
  should have values filled in from the identity sequence.  The coding using
  build_column_default() fails for this because the sequence ownership isn't
  registered until after ALTER TABLE, and we can't do it before because we don't
  have the column in the catalog yet.  So we specially remember in ColumnDef the
  sequence name that we decided on and build a custom NextValueExpr using that.
  Reviewed-by: Michael Paquier <michael(dot)paquier(at)gmail(dot)com>
  https://git.postgresql.org/pg/commitdiff/533c5d8bddf0feb1785b3da17c0d17feeaac76d8

- doc: Fix index link.  The index entry was pointing to a slightly wrong
  location.
  https://git.postgresql.org/pg/commitdiff/bc38bdba04d75f7c39d57f3eba9c01958d8d2f7c

- doc: Clarify psql --list documentation a bit more.
  https://git.postgresql.org/pg/commitdiff/1d81c093db81f63727436c736d9d27b7bedb4b66

- doc: Fix name in release notes.  Author: Alexander Lakhin
  <exclusion(at)gmail(dot)com>
  https://git.postgresql.org/pg/commitdiff/4ac583f36a0c5452047531f56703b8ea51e718ad

Robert Haas pushed:

- Fix test case for 'outer pathkeys do not match mergeclauses' fix.  Commit
  4bbf6edfbd5d03743ff82dda2f00c738fb3208f5 added a test case, but it turns out
  that the test case doesn't reliably test for the bug, and in the context of
  the regression test suite did not because ANALYZE had not been run.  Report
  and patch by Etsuro Fujita.  I added a comment along lines previously
  suggested by Tom Lane.  Discussion:
  http://postgr.es/m/5A6195D8.8060206@lab.ntt.co.jp
  https://git.postgresql.org/pg/commitdiff/99f6a17dd62aa5ed92df7e5c03077ddfc85381c8

- pg_prewarm: Add missing LWLockRegisterTranche call.  Commit
  79ccd7cbd5ca44bee0191d12e9e65abf702899e7, which added automatic prewarming,
  neglected this.  Kyotaro Horiguchi, reviewed by me.  Discussion:
  http://postgr.es/m/20171215.173219.38055760.horiguchi.kyotaro@lab.ntt.co.jp
  https://git.postgresql.org/pg/commitdiff/0ff5bd7b47377a6b5939d6fbbb67c8d42f9170dc

- Fix list partition constraints for partition keys of array type.  The old code
  generated always generated a constraint of the form col = ANY(ARRAY[val1,
  val2, ...]), but that's invalid when col is an array type.  Instead, generate
  col = val when there's only one value, col = val1 OR col = val2 OR ... when
  there are multiple values and col is of array type, and the old form when
  there are multiple values and col is not of an array type.  As a side benefit,
  this makes constraint exclusion able to prune a list partition declared to
  accept a single Boolean value, which didn't work before.  Amit Langote,
  reviewed by Etsuro Fujita Discussion:
  http://postgr.es/m/97267195-e235-89d1-a41a-c110198dfce9@lab.ntt.co.jp
  https://git.postgresql.org/pg/commitdiff/3ccdc6f9a5876d0953912fd589989387764ed9a3

- pgcrypto's encrypt() supports AES-128, AES-192, and AES-256.  Previously, only
  128 was mentioned, but the others are also supported.  Thomas Munro, reviewed
  by Michael Paquier and extended a bit by me.  Discussion:
  http://postgr.es/m/CAEepm=1XbBHXYJKofGjnM2Qfz-ZBVqhGU4AqvtgR+Hegy4fdKg@mail.gmail.com
  https://git.postgresql.org/pg/commitdiff/d40d97d6c74496a35111b29f8eef2a09cb43bc58

- Fix typo: colums -> columns.  Along the way, also fix code indentation.
  Alexander Lakhin, reviewed by Michael Paquier Discussion:
  http://postgr.es/m/45c44aa7-7cfa-7f3b-83fd-d8300677fdda@gmail.com
  https://git.postgresql.org/pg/commitdiff/22757960bb3b2a6fa331bad132998c53b3e744a9

- Fix possible failure to mark hash metapage dirty.  Report and suggested fix by
  Lixian Zou.  Amit Kapila put it in the form of a patch and reviewed.
  Discussion:
  http://postgr.es/m/151739848647.1239.12528851873396651946@wrigleys.postgresql.org
  https://git.postgresql.org/pg/commitdiff/ad25a6b1f25baf09c869c903c9c8e26d390875f5

- Add new function WaitForParallelWorkersToAttach.  Once this function has been
  called, we know that all workers have started and attached to their error
  queues -- so if any of them subsequently exit uncleanly, we'll be sure to
  throw an ERROR promptly.  Otherwise, users of the ParallelContext machinery
  must be careful not to wait forever for a worker that has failed to start.
  Parallel query manages to work without needing this for reasons explained in
  new comments added by this patch, but it's a useful primitive for other
  parallel operations, such as the pending patch to make creating a btree index
  run in parallel.  Amit Kapila, revised by me.  Additional review by Peter
  Geoghegan.  Discussion:
  http://postgr.es/m/CAA4eK1+e2MzyouF5bg=OtyhDSX+=Ao=3htN=T-r_6s3gCtKFiw@mail.gmail.com
  https://git.postgresql.org/pg/commitdiff/9222c0d9ed9794d54fc3f5101498829eaec9e799

- Refactor code for partition bound searching.  Remove partition_bound_cmp() and
  partition_bound_bsearch(), whose void * argument could be, depending on the
  situation, of any of three different types: PartitionBoundSpec *,
  PartitionRangeBound *, Datum *.  Instead, introduce separate bound-searching
  functions for each situation: partition_list_bsearch, partition_range_bsearch,
  partition_range_datum_bsearch, and partition_hash_bsearch.  This requires
  duplicating the code for binary search, but it makes the code much more type
  safe, involves fewer branches at runtime, and at least in my opinion, is much
  easier to understand.  Along the way, add an option to
  partition_range_datum_bsearch allowing the number of keys to be specified, so
  that we can search for partitions based on a prefix of the full list of
  partition keys.  This is important for pending work to improve partition
  pruning.  Amit Langote, per a suggestion from me.  Discussion:
  http://postgr.es/m/CA+TgmoaVLDLc8=YESRwD32gPhodU_ELmXyKs77gveiYp+JE4vQ@mail.gmail.com
  https://git.postgresql.org/pg/commitdiff/9aef173163ae68c6b241e4c9bbb375c6baa71c60

- Support parallel btree index builds.  To make this work, tuplesort.c and
  logtape.c must also support parallelism, so this patch adds that
  infrastructure and then applies it to the particular case of parallel btree
  index builds.  Testing to date shows that this can often be 2-3x faster than a
  serial index build.  The model for deciding how many workers to use is fairly
  primitive at present, but it's better than not having the feature.  We can
  refine it as we get more experience.  Peter Geoghegan with some help from
  Rushabh Lathia.  While Heikki Linnakangas is not an author of this patch, he
  wrote other patches without which this feature would not have been possible,
  and therefore the release notes should possibly credit him as an author of
  this feature.  Reviewed by Claudio Freire, Heikki Linnakangas, Thomas Munro,
  Tels, Amit Kapila, me.  Discussion:
  http://postgr.es/m/CAM3SWZQKM=Pzc=CAHzRixKjp2eO5Q0Jg1SoFQqeXFQ647JiwqQ@mail.gmail.com
  Discussion:
  http://postgr.es/m/CAH2-Wz=AxWqDoVvGU7dq856S4r6sJAj6DBn7VMtigkB33N5eyg@mail.gmail.com
  https://git.postgresql.org/pg/commitdiff/9da0cc35284bdbe8d442d732963303ff0e0a40bc

Bruce Momjian pushed:

- doc:  mention datadir locations are actually config locations.  Technically,
  pg_upgrade's --old-datadir and --new-datadir are configuration directories,
  not necessarily data directories.  This is reflected in the 'postgres' manual
  page, so do the same for pg_upgrade.  Reported-by: Yves Goergen Bug: 14898
  Discussion:
  https://postgr.es/m/20171110220912.31513.13322@wrigleys.postgresql.org
  Backpatch-through: 10
  https://git.postgresql.org/pg/commitdiff/e5dede90971d2ddbb7bca72ffc329c043bf717db

- doc: Improve pg_upgrade rsync examples to use clusterdir.  Commit
  9521ce4a7a1125385fb4de9689f345db594c516a from Sep 13, 2017 and backpatched
  through 9.5 used rsync examples with datadir.  The reporter has pointed out,
  and testing has verified, that clusterdir must be used, so update the docs
  accordingly.  Reported-by: Don Seiler Discussion:
  https://postgr.es/m/CAHJZqBD0u9dCERpYzK6BkRv=663AmH==DFJpVC=M4Xg_rq2=CQ@mail.gmail.com
  Backpatch-through: 9.5
  https://git.postgresql.org/pg/commitdiff/de715414608846ce1ae44b79a39d61c48e25dce7

- doc:  in contrib-spi, mention and link to the meaning of SPI.  Also remove
  outdated comment about SPI subtransactions.  Reported-by: gregory(at)arenius(dot)com
  Discussion:
  https://postgr.es/m/151726276676.1240.10501743959198501067@wrigleys.postgresql.org
  Backpatch-through: 9.3
  https://git.postgresql.org/pg/commitdiff/3b15255912af3fa428fbc296d830292ffc8c9803

- doc:  clearify trigger behavior for inheritance.  The previous wording added
  in PG 10 wasn't specific enough about the behavior of statement and row
  triggers when using inheritance.  Reported-by: ian(at)thepathcentral(dot)com
  Discussion:
  https://postgr.es/m/20171129193934.27108.30796@wrigleys.postgresql.org
  Backpatch-through: 10
  https://git.postgresql.org/pg/commitdiff/1cf1112990cff432b53a74a0ac9ca897ce8a7688

- doc:  clarify major/minor pg_upgrade versions with examples.  The previous
  docs added in PG 10 were not clear enough for someone who didn't understand
  the PG 10 version change, so give more specific examples.  Reported-by:
  jim(at)room118solutions(dot)com Discussion:
  https://postgr.es/m/20171218213041.25744.8414@wrigleys.postgresql.org
  Backpatch-through: 10
  https://git.postgresql.org/pg/commitdiff/59ad2463507622a1244740c4b527610f590dc473

- doc:  fix trigger inheritance wording.  Fix wording from commit
  1cf1112990cff432b53a74a0ac9ca897ce8a7688 Reported-by: Robert Haas
  Backpatch-through: 10
  https://git.postgresql.org/pg/commitdiff/eab30cc6b55dc03589bda13bc76b12d7142d5686

- psql:  Add quit/help behavior/hint, for other tool portability.  Issuing
  'quit'/'exit' in an empty psql buffer exits psql.  Issuing 'quit'/'exit' in a
  non-empty psql buffer alone on a line with no prefix whitespace issues a hint
  on how to exit.  Also add similar 'help' hints for 'help' in a non-empty psql
  buffer.  Reported-by: Everaldo Canuto Discussion:
  https://postgr.es/m/flat/CALVFHFb-C_5_94hueWg6Dd0zu7TfbpT7hzsh9Zf0DEDOSaAnfA%40mail.gmail.com
  Author: original author Robert Haas, modified by me
  https://git.postgresql.org/pg/commitdiff/df9f599bc6f14307252ac75ea1dc997310da5ba6

Stephen Frost pushed:

- Improve ALTER TABLE synopsis.  Add into the ALTER TABLE synopsis the
  definition of partition_bound_spec, column_constraint, index_parameters and
  exclude_element.  Initial patch by Lætitia Avrot, with further improvements by
  Amit Langote and Thomas Munro.  Discussion:
  https://postgr.es/m/flat/27ec4df3-d1ab-3411-f87f-647f944897e1%40lab.ntt.co.jp
  https://git.postgresql.org/pg/commitdiff/a2a22057617dc84b500f85938947c125183f1289

== Pending Patches ==

Yuto Hayamizu sent in another revision of a patch to fix overestimated filter
cost.

Amit Langote sent in two revisions of a patch to include the new local
partitioned indexes in the CREATE INDEX documentation.

Kyotaro HORIGUCHI sent in two more revisions of a patch to add a WAL relief
valve for replication slots, add monitoring for replication slots, add a TAP
test for the slot limit feature, and document same.

Ildar Musin sent in another revision of a patch to add general purpose hashing
functions to pgbench.

Ildus Kurbangaliev sent in another revision of a patch to add custom compression
methods.

Konstantin Knizhnik sent in two more revisions of a patch to optimize secondary
index access.

Nikhil Sontakke sent in another revision of a patch to implement logical
decoding of two-phase transactions.

David Steele sent in another revision of a patch to implement a configurable
file mode mask.

Andres Freund sent in a patch to deconflict datetime.h macro names.

Etsuro Fujita sent in another revision of a patch to change how a list partition
constraint is emitted.

David Rowley sent in another revision of a patch to allow deciding whether
STATISTICS are included in CREATE TABLE LIKE.

Amit Langote sent in a patch to fix what had appeared to be a bug in local
indexes on partitioned tables.

Robert Haas sent in two more revisions of a patch to account for parallel paths
tlist cost.

Jeevan Chalke sent in two more revisions of a patch to implement partition-wise
aggregation/grouping.

Yugo Nagata sent in three more revisions of a patch to implement lockable views.

Amit Langote sent in another revision of a patch to create a syntax for boolean
partitions.

Simon Riggs sent in two more revisions of a patch to implement MERGE.

Oliver Ford and Tom Lane traded patches to implement RANGE with values and
exclusions clauses to windowing functions.

John Naylor sent in another revision of a patch to refactor bootstrap data for
sanity and legibility.

Doug Rady sent in a patch to refactor all of the connection state PQfinish() and
NULL’ing into a single function, except for PQfinish() in doConnect().

Anastasia Lubennikova sent in another revision of a patch to implement covering
and unique indexes.

Dmitry Dolgov sent in another revision of a patch to implement generic type
subscripting and use same for arrays and JSONB.

Daniel Vérité sent in a patch to add a CSV output format to psql.

Peter Eisentraut sent in another revision of a patch to support GnuTLS.

Kyotaro HORIGUCHI, Amit Langote and David Rowley traded patches to speed up
partition pruning.

Haozhou Wang sent in a patch to add missing type conversion functions for
PL/Python.

Michail Nikolaev sent in a patch to optimize OFFSET with IndexScan using the
visibility map.

Yugo Nagata sent in two revisions of a patch to fix an infelicity between
CURRENT OF and IndexOnlyScan.

Michaël Paquier sent in another revision of a patch to refactor the syscache
routines to get attribute name, extend the lookup routines for FDW and foreign
server with NULL handling, refactor the routines for subscription and
publication lookups, and eliminate user-visible cache lookup errors for objaddr
SQL functions.

Anton Dignös sent in a patch to fix an IndexJoin memory problem using SP-GiST
and boxes.

Amit Langote sent in a patch to disregard nulls in SAOP rightarg array/list
during CE.

Kyotaro HORIGUCHI sent in a patch to fix line_perp() (?-|).

Amit Langote sent in another revision of a patch to teach
operator_predicate_proof() to strip RelabelType.

Peter Eisentraut sent in a patch to fix a bug which caused cancelling parallel
query to lead to a segfault.

Amit Kapila sent in a patch to ensure that MarkBufferDirty is called at the
appropriate place in the hash index code.

Michael Banck sent in a patch to allow pg_dump to /dev/null.

Artur Zakirov sent in another revision of a patch to fix a bug in
to_timestamp() where formats weren't checked correctly.

Dean Rasheed sent in a patch to improve MCV lists for highly skewed
distributions.

Marina Polyakova sent in another revision of a patch to precalculate stable and
immutable functions.

Takayuki Tsunakawa sent in a patch to fix a bug in ECPG where freeing memory for
pgtypes would crash on Windows.

Michaël Paquier sent in another revision of a patch to create backup history
files for backups taken from standbys.

Aleksandr Parfenov sent in another revision of a patch to create a more flexible
configuration for full-text search.

Ildus Kurbangaliev sent in a patch to implement a prefix operator, ^@, for text
and give it SP-GiST support.

Konstantin Knizhnik sent in another revision of a patch to implement built-in
connection pooling.

Peter Geoghegan sent in a patch to add logtape.c Valgrind suppression.

Pavel Stěhule and David G. Johnson traded patches to implement schema variables.

Pierre Ducroquet sent in a patch to add support for LLVM 4 and LLVM 5 atop the
JIT patch.

Pierre Ducroquet sent in a patch to fix support for LLVM 3.9 atop the JIT patch.

Amul Sul sent in another revision of a patch to restrict concurrent
UPDATEs and DELETEs during the UPDATE of a partition key.


pgsql-announce by date

Next:From: Bal Krishna BalDate: 2018-02-05 01:19:16
Subject: Fwd: Call for papers for PGCONF Nepal 2018 - Deadline extended to Feb 15, 2018
Previous:From: Tung ThanhDate: 2018-02-02 08:48:42
Subject: Announcing TablePlus, a modern, native tool for relational database on Mac

Privacy Policy | About PostgreSQL
Copyright © 1996-2018 The PostgreSQL Global Development Group