On Windows, ensure shared memory handle gets closed if not being used.
Postmaster child processes that aren't supposed to be attached to shared
memory were not bothering to close the shared memory mapping handle they
inherit from the postmaster process. That's mostly harmless, since the
handle va
On Windows, ensure shared memory handle gets closed if not being used.
Postmaster child processes that aren't supposed to be attached to shared
memory were not bothering to close the shared memory mapping handle they
inherit from the postmaster process. That's mostly harmless, since the
handle va
On Windows, ensure shared memory handle gets closed if not being used.
Postmaster child processes that aren't supposed to be attached to shared
memory were not bothering to close the shared memory mapping handle they
inherit from the postmaster process. That's mostly harmless, since the
handle va
On Windows, ensure shared memory handle gets closed if not being used.
Postmaster child processes that aren't supposed to be attached to shared
memory were not bothering to close the shared memory mapping handle they
inherit from the postmaster process. That's mostly harmless, since the
handle va
On Windows, ensure shared memory handle gets closed if not being used.
Postmaster child processes that aren't supposed to be attached to shared
memory were not bothering to close the shared memory mapping handle they
inherit from the postmaster process. That's mostly harmless, since the
handle va
On Windows, ensure shared memory handle gets closed if not being used.
Postmaster child processes that aren't supposed to be attached to shared
memory were not bothering to close the shared memory mapping handle they
inherit from the postmaster process. That's mostly harmless, since the
handle va
Improve INSERT .. ON CONFLICT error message.
Peter Geoghegan, reviewed by me.
Branch
--
REL9_5_STABLE
Details
---
http://git.postgresql.org/pg/commitdiff/bf8a361e101d830a6db105982a8527325c2e85fc
Modified Files
--
src/backend/executor/execIndexing.c|4 ++--
src/tes
Improve INSERT .. ON CONFLICT error message.
Peter Geoghegan, reviewed by me.
Branch
--
master
Details
---
http://git.postgresql.org/pg/commitdiff/b8dd19af50950d4933da7ad60f93388e9d0eb851
Modified Files
--
src/backend/executor/execIndexing.c|4 ++--
src/test/regre
Have dtrace depend on object files directly, not objfiles.txt
Per Mark Johnston, this resolves a build error on FreeBSD related
to the fact that dtrace is modifying the generated object files
under the hood. Consequently, without this, dtrace gets reinvoked
at install time because the object file
-- email subject limit -
-- gitweb summary limit --
pg_upgrade: reorder controldata checks to match program output
Also improve comment for how float8_pass_by_value is used.
Backpatch through 9.5
Branch
--
master
Details
-
-- email subject limit -
-- gitweb summary limit --
pg_upgrade: reorder controldata checks to match program output
Also improve comment for how float8_pass_by_value is used.
Backpatch through 9.5
Branch
--
REL9_5_STABLE
Detail
On Tue, Oct 13, 2015 at 10:25:37PM +, Bruce Momjian wrote:
> -- email subject limit -
> -- gitweb summary limit --
> pg_upgrade: reorder controldata checks to match program output
>
> Also improve comment for how float8_pass_by_v
12 matches
Mail list logo
