Robert Haas b40b4dd9e1 Reserve zero as an invalid DSM handle. ...

Previously, the handle for the control segment could not be zero, but
some other DSM segment could potentially have a handle value of zero.
However, that means that if someone wanted to store a dsm_handle that
might or might not be valid, they would need a separate boolean to
keep track of whether the associated value is legal.  That's annoying,
so change things so that no DSM segment can ever have a handle of 0 -
or as we call it here, DSM_HANDLE_INVALID.

Thomas Munro.  This was submitted as part of a much larger patch to
add an malloc-like allocator for dynamic shared memory, but this part
seems like a good idea independently of the rest of the patch.

2016-11-15 16:33:29 -05:00

..

buffer

Add API to check if an existing exclusive lock allows cleanup.

2016-11-04 09:32:24 -04:00

file

Rename "pg_xlog" directory to "pg_wal".

2016-10-20 11:32:18 -04:00

freespace

Fix WAL-logging of FSM and VM truncation.

2016-10-19 14:26:05 +03:00

ipc

Reserve zero as an invalid DSM handle.

2016-11-15 16:33:29 -05:00

large_object

Update copyright for 2016

2016-01-02 13:33:40 -05:00

lmgr

Rename WAIT_* constants to PG_WAIT_*.

2016-10-05 08:04:52 -04:00

page

Rewrite PageIndexDeleteNoCompact into a form that only deletes 1 tuple.

2016-09-09 19:00:59 -04:00

smgr

Improve scalability of md.c for large relations.

2016-09-08 17:18:46 -07:00

Makefile

Remove cvs keywords from all files.

2010-09-20 22:08:53 +02:00