Fix inaccurate description of tablespace.
Currently we don't need to update the pg_tablespace catalog
after redefining the symbolic links to the tablespaces
because pg_tablespace.spclocation column was removed in
PostgreSQL 9.2.
Back patch to 9.2 where pg_tablespace.spclocation was removed.
Ian
Fix inaccurate description of tablespace.
Currently we don't need to update the pg_tablespace catalog
after redefining the symbolic links to the tablespaces
because pg_tablespace.spclocation column was removed in
PostgreSQL 9.2.
Back patch to 9.2 where pg_tablespace.spclocation was removed.
Ian
Fix inaccurate description of tablespace.
Currently we don't need to update the pg_tablespace catalog
after redefining the symbolic links to the tablespaces
because pg_tablespace.spclocation column was removed in
PostgreSQL 9.2.
Back patch to 9.2 where pg_tablespace.spclocation was removed.
Ian
Fix typo in comment.
Hitoshi Harada
Branch
--
master
Details
---
http://git.postgresql.org/pg/commitdiff/c876fb42417739dbb19540ef61f6cd75752eb16e
Modified Files
--
src/backend/storage/ipc/sinvaladt.c |2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
--
Sent via
Fix regexp_matches() handling of zero-length matches.
We'd find the same match twice if it was of zero length and not immediately
adjacent to the previous match. replace_text_regexp() got similar cases
right, so adjust this search logic to match that. Note that even though
the
Fix regexp_matches() handling of zero-length matches.
We'd find the same match twice if it was of zero length and not immediately
adjacent to the previous match. replace_text_regexp() got similar cases
right, so adjust this search logic to match that. Note that even though
the
Fix regexp_matches() handling of zero-length matches.
We'd find the same match twice if it was of zero length and not immediately
adjacent to the previous match. replace_text_regexp() got similar cases
right, so adjust this search logic to match that. Note that even though
the
Fix regexp_matches() handling of zero-length matches.
We'd find the same match twice if it was of zero length and not immediately
adjacent to the previous match. replace_text_regexp() got similar cases
right, so adjust this search logic to match that. Note that even though
the
Fix regexp_matches() handling of zero-length matches.
We'd find the same match twice if it was of zero length and not immediately
adjacent to the previous match. replace_text_regexp() got similar cases
right, so adjust this search logic to match that. Note that even though
the
Fix regexp_matches() handling of zero-length matches.
We'd find the same match twice if it was of zero length and not immediately
adjacent to the previous match. replace_text_regexp() got similar cases
right, so adjust this search logic to match that. Note that even though
the
pg_dump/pg_dumpall: remove unnecessary SQL trailing semicolons
Patch by Ian Lawrence Barwick
Branch
--
master
Details
---
http://git.postgresql.org/pg/commitdiff/8eb29194fc1711308804e8d4238a002a1cd35afe
Modified Files
--
src/bin/pg_dump/pg_dump.c|1 -
Fix a couple of inconsequential typos in new header
Branch
--
master
Details
---
http://git.postgresql.org/pg/commitdiff/3142cf6dd5c0308633e36fabbd13bb51bdec1ff2
Modified Files
--
src/include/postmaster/bgworker_internals.h |4 ++--
1 file changed, 2 insertions(+), 2
Fix mis-indented lines
Per Coverity
Branch
--
master
Details
---
http://git.postgresql.org/pg/commitdiff/a59516b6311a6c2acc89448c94913ebae598f02a
Modified Files
--
src/backend/utils/misc/guc-file.l |6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
--
Sent via
Fix mis-indented lines
Per Coverity
Branch
--
REL9_3_STABLE
Details
---
http://git.postgresql.org/pg/commitdiff/603c4a90c15f601ccf44cad3d3b04b39e4dc34eb
Modified Files
--
src/backend/utils/misc/guc-file.l |6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
--
Allow a context to be passed in for error handling
As pointed out by Tom Lane, we can allow other users of the error
handler callbacks to provide their own memory context by adding
the context to use to ErrorData and using that instead of explicitly
using ErrorContext.
This then allows
Add locking around SSL_context usage in libpq
I've been working with Nick Phillips on an issue he ran into when
trying to use threads with SSL client certificates. As it turns out,
the call in initialize_SSL() to SSL_CTX_use_certificate_chain_file()
will modify our SSL_context without any
Add locking around SSL_context usage in libpq
I've been working with Nick Phillips on an issue he ran into when
trying to use threads with SSL client certificates. As it turns out,
the call in initialize_SSL() to SSL_CTX_use_certificate_chain_file()
will modify our SSL_context without any
Add locking around SSL_context usage in libpq
I've been working with Nick Phillips on an issue he ran into when
trying to use threads with SSL client certificates. As it turns out,
the call in initialize_SSL() to SSL_CTX_use_certificate_chain_file()
will modify our SSL_context without any
Add locking around SSL_context usage in libpq
I've been working with Nick Phillips on an issue he ran into when
trying to use threads with SSL client certificates. As it turns out,
the call in initialize_SSL() to SSL_CTX_use_certificate_chain_file()
will modify our SSL_context without any
Add locking around SSL_context usage in libpq
I've been working with Nick Phillips on an issue he ran into when
trying to use threads with SSL client certificates. As it turns out,
the call in initialize_SSL() to SSL_CTX_use_certificate_chain_file()
will modify our SSL_context without any
20 matches
Mail list logo
