Fix bug in the new wait-until-lwlock-is-free mechanism.
If there was a wait-until-free process in the head of the wait queue,
followed by an exclusive locker, the exclusive locker was not be woken up
as it should.
Branch
--
master
Details
---
http://git.postgresql.org/pg/commitdiff/82d4b
Use abort() instead of exit() to abort library functions
In some hopeless situations, certain library functions in libpq and
libpgport quit the program. Use abort() for that instead of exit(),
so we don't interfere with the normal exit codes the program might
use, we clearly signal the abnormal t
PL/Python: Add result metadata functions
Add result object functions .colnames, .coltypes, .coltypmods to
obtain information about the result column names and types, which was
previously not possible in the PL/Python SPI interface.
reviewed by Abhijit Menon-Sen
Branch
--
master
Details
Add sequence USAGE privileges to information schema
The sequence USAGE privilege is sufficiently similar to the SQL
standard that it seems reasonable to show in the information schema.
Also add some compatibility notes about it on the GRANT reference
page.
Branch
--
master
Details
---
ht
Remove prototype for nonexistent function.
Branch
--
master
Details
---
http://git.postgresql.org/pg/commitdiff/423ee49b491ee966aa06259772dc38819cab786a
Modified Files
--
src/bin/pg_dump/pg_dump.h |1 -
1 files changed, 0 insertions(+), 1 deletions(-)
--
Sent via pgsql-
Andrew Dunstan writes:
> On 01/30/2012 10:45 AM, Tom Lane wrote:
>> Another aspect of this is that when the same-or-almost-the-same patch
>> is applied to multiple branches, it's a *lot* easier for future
>> archeology in the commit logs if the patch goes into all the affected
>> branches at th
On 01/30/2012 10:45 AM, Tom Lane wrote:
Another aspect of this is that when the same-or-almost-the-same patch
is applied to multiple branches, it's a *lot* easier for future
archeology in the commit logs if the patch goes into all the affected
branches at the same time (and with the same comm
Robert Haas writes:
> On Mon, Jan 30, 2012 at 4:13 AM, Simon Riggs wrote:
>> On Mon, Jan 30, 2012 at 12:30 AM, Tom Lane wrote:
>>> I see this was only applied to HEAD. Wouldn't back-patching be in
>>> order? The problem is in 9.1 as well, no?
>> Yes, it is. I prefer to give a little time befo
Make group commit more effective.
When a backend needs to flush the WAL, and someone else is already flushing
the WAL, wait until it releases the WALInsertLock and check if we still need
to do the flush or if the other backend already did the work for us, before
acquiring WALInsertLock. This helps
Minor bug fix and cleanup from self-review of sync rep queues patch.
Branch
--
master
Details
---
http://git.postgresql.org/pg/commitdiff/ba1868ba3138b2119f8290969b9a3936fbc297ce
Modified Files
--
src/backend/postmaster/checkpointer.c |2 +-
src/backend/postmaster/postmast
Various minor comments changes from bgwriter to checkpointer.
Branch
--
master
Details
---
http://git.postgresql.org/pg/commitdiff/73f617f13f4ca185977d9f7b09bf9edc491cd12f
Modified Files
--
src/backend/postmaster/checkpointer.c | 18 +-
src/backend/repl
On Mon, Jan 30, 2012 at 4:13 AM, Simon Riggs wrote:
> On Mon, Jan 30, 2012 at 12:30 AM, Tom Lane wrote:
>> Simon Riggs writes:
>>> Resolve timing issue with logging locks for Hot Standby.
>>> We log AccessExclusiveLocks for replay onto standby nodes,
>>> but because of timing issues on ProcArray
Accept a non-existent value in "ALTER USER/DATABASE SET ..." command.
When default_text_search_config, default_tablespace, or temp_tablespaces
setting is set per-user or per-database, with an "ALTER USER/DATABASE SET
..." statement, don't throw an error if the text search configuration or
tablespa
Accept a non-existent value in "ALTER USER/DATABASE SET ..." command.
When default_text_search_config, default_tablespace, or temp_tablespaces
setting is set per-user or per-database, with an "ALTER USER/DATABASE SET
..." statement, don't throw an error if the text search configuration or
tablespa
Accept a non-existent value in "ALTER USER/DATABASE SET ..." command.
When default_text_search_config, default_tablespace, or temp_tablespaces
setting is set per-user or per-database, with an "ALTER USER/DATABASE SET
..." statement, don't throw an error if the text search configuration or
tablespa
Accept a non-existent value in "ALTER USER/DATABASE SET ..." command.
When default_text_search_config, default_tablespace, or temp_tablespaces
setting is set per-user or per-database, with an "ALTER USER/DATABASE SET
..." statement, don't throw an error if the text search configuration or
tablespa
Accept a non-existent value in "ALTER USER/DATABASE SET ..." command.
When default_text_search_config, default_tablespace, or temp_tablespaces
setting is set per-user or per-database, with an "ALTER USER/DATABASE SET
..." statement, don't throw an error if the text search configuration or
tablespa
On Mon, Jan 30, 2012 at 12:30 AM, Tom Lane wrote:
> Simon Riggs writes:
>> Resolve timing issue with logging locks for Hot Standby.
>> We log AccessExclusiveLocks for replay onto standby nodes,
>> but because of timing issues on ProcArray it is possible to
>> log a lock that is still held by a ju
Log Message:
---
Fix bug: json_check not crash if json is null
float functions return json datatype int and int functions return datatype float
Modified Files:
--
postgresql-json/src:
postgres_json.c (r1.1 -> r1.2)
(http://cvs.pgfoundry.org/cgi-bin/cvsweb.c
19 matches
Mail list logo
