Change errcode for lock_timeout to match NOWAIT
Set errcode to ERRCODE_LOCK_NOT_AVAILABLE
Zoltán Bsöszörményi
Branch
--
master
Details
---
http://git.postgresql.org/pg/commitdiff/d51b271059ba736f71c5372f713d907f711208ec
Modified Files
--
src/backend/tcop/postgres.c |2 +
Change errcode for lock_timeout to match NOWAIT
Set errcode to ERRCODE_LOCK_NOT_AVAILABLE
Zoltán Bsöszörményi
Branch
--
REL9_3_STABLE
Details
---
http://git.postgresql.org/pg/commitdiff/452d0c21825dd52c10af4538d850991bf6a00e38
Modified Files
--
src/backend/tcop/postgres.c |
Assert that ALTER TABLE subcommands have pass set
Branch
--
master
Details
---
http://git.postgresql.org/pg/commitdiff/2f74e4ec50dc625605e9a7afd63bd8a48c981d9e
Modified Files
--
src/backend/commands/tablecmds.c |6 --
1 file changed, 4 insertions(+), 2 deletions(-)
-
ALTER TABLE ... ALTER CONSTRAINT for FKs
Allow constraint attributes to be altered,
so the default setting of NOT DEFERRABLE
can be altered to DEFERRABLE and back.
Review by Abhijit Menon-Sen
Branch
--
master
Details
---
http://git.postgresql.org/pg/commitdiff/f177cbfe676dc2c7ca2b206c54
pg_upgrade: pass username to analyze script
If -U (user) is specified, pass the username into the created analyze
script.
Per request from Ray Stell
Branch
--
master
Details
---
http://git.postgresql.org/pg/commitdiff/f85136106d87f54e87635736dfe1b8227b6803ad
Modified Files
-
pg_upgrade: remove -h option
-h (help) is not needed; pg_upgrade already supports --help and -?,
which is consistent with other tools.
Branch
--
master
Details
---
http://git.postgresql.org/pg/commitdiff/e029275cdeb39cd2178ac23e2fcc65520f7b7b9c
Modified Files
--
contrib/pg_
pg_upgrade: trim down --help and doc option descriptions
Previous code had old/new prefixes on option values, e.g.
--old-datadir=OLDDATADIR. Remove them, for simplicity; now:
--old-datadir=DATADIR. Also update docs to do the same.
Branch
--
master
Details
---
http://git.postgresql.org
Send SIGKILL to children if they don't die quickly in immediate shutdown
On immediate shutdown, or during a restart-after-crash sequence,
postmaster used to send SIGQUIT (and then abandon ship if shutdown); but
this is not a good strategy if backends don't die because of that
signal. (This might
pg_upgrade: change -u to -U, for consistency
Change -u (user) option to -U, for consistency with other tools like
pg_dump and psql. Also expand --user to --username, again for
consistency.
BACKWARD INCOMPATIBILITY
Branch
--
master
Details
---
http://git.postgresql.org/pg/commitdiff/457d
Make the OVER keyword unreserved.
This results in a slightly less specific error message when OVER
is used in a context where we don't accept window functions, but
per discussion, it's worth it to get the benefit of not needing
to reserve this keyword any more. This same refactoring will
also let
Define Trap and TrapMacro even in non-cassert builds.
In some cases, the use of these macros may be preferable to Assert()
or AssertMacro(), since this way the caller can set the trap message.
Andres Freund and Robert Haas
Branch
--
master
Details
---
http://git.postgresql.org/pg/commit
Track spinlock delay in microsecond granularity.
On many platforms the OS will round the sleep time to millisecond
resolution, but there is no reason for us to pre-emptively round the
argument to pg_usleep.
When the delay was measured in milliseconds and started from 1 ms, it
sometimes took many
12 matches
Mail list logo