pgsql: Remove bogus "extern" annotations on function definitions.

Remove bogus "extern" annotations on function definitions. While this is not illegal C, project style is to put "extern" only on declarations not definitions. David Rowley Discussion: https://postgr.es/m/cakjs1f9rklwxcmbqhvdyhmsmeo+alunga-ne+ax5uoke9dj...@mail.gmail.com Branch -- master D

pgsql: Allow UNIQUE indexes on partitioned tables

Allow UNIQUE indexes on partitioned tables If we restrict unique constraints on partitioned tables so that they must always include the partition key, then our standard approach to unique indexes already works --- each unique key is forced to exist within a single partition, so enforcing the uniqu

pgsql: Fix expected output

Fix expected output Branch -- master Details --- https://git.postgresql.org/pg/commitdiff/4108a28d3a02c4226b0f558cf00738e00e8ea2a1 Modified Files -- src/test/regress/expected/indexing.out | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-)

pgsql: Fix misbehavior of CTE-used-in-a-subplan during EPQ rechecks.

Fix misbehavior of CTE-used-in-a-subplan during EPQ rechecks. An updating query that reads a CTE within an InitPlan or SubPlan could get incorrect results if it updates rows that are concurrently being modified. This is caused by CteScanNext supposing that nothing inside its recursive ExecProcNode

pgsql: Fix misbehavior of CTE-used-in-a-subplan during EPQ rechecks.

Fix misbehavior of CTE-used-in-a-subplan during EPQ rechecks. An updating query that reads a CTE within an InitPlan or SubPlan could get incorrect results if it updates rows that are concurrently being modified. This is caused by CteScanNext supposing that nothing inside its recursive ExecProcNode

pgsql: Fix misbehavior of CTE-used-in-a-subplan during EPQ rechecks.

Fix misbehavior of CTE-used-in-a-subplan during EPQ rechecks. An updating query that reads a CTE within an InitPlan or SubPlan could get incorrect results if it updates rows that are concurrently being modified. This is caused by CteScanNext supposing that nothing inside its recursive ExecProcNode

pgsql: Fix misbehavior of CTE-used-in-a-subplan during EPQ rechecks.

Fix misbehavior of CTE-used-in-a-subplan during EPQ rechecks. An updating query that reads a CTE within an InitPlan or SubPlan could get incorrect results if it updates rows that are concurrently being modified. This is caused by CteScanNext supposing that nothing inside its recursive ExecProcNode

pgsql: Fix misbehavior of CTE-used-in-a-subplan during EPQ rechecks.

Fix misbehavior of CTE-used-in-a-subplan during EPQ rechecks. An updating query that reads a CTE within an InitPlan or SubPlan could get incorrect results if it updates rows that are concurrently being modified. This is caused by CteScanNext supposing that nothing inside its recursive ExecProcNode

pgsql: Fix misbehavior of CTE-used-in-a-subplan during EPQ rechecks.

Fix misbehavior of CTE-used-in-a-subplan during EPQ rechecks. An updating query that reads a CTE within an InitPlan or SubPlan could get incorrect results if it updates rows that are concurrently being modified. This is caused by CteScanNext supposing that nothing inside its recursive ExecProcNode

pgsql: Fix crash in pg_replication_slot_advance

Fix crash in pg_replication_slot_advance We were trying to use a LSN variable after releasing its containing slot structure. Reported by: tushar Author: amul sul Reviewed-by: Petr Jelinek, Masahiko Sawada Discussion: https://postgr.es/m/[email protected] Bran