Re: [HACKERS] SSL certificate location
## Terence Ferraro (terencejferr...@gmail.com): > At the moment, if a user has multiple applications on a single machine > connecting with different SSL certificates, each process must be launched > by a different logical user and the certificates placed within that user's > home directory (and this is just for *nix, forget about Windows). The > current method is not scalable, either. That is incorrect. http://www.postgresql.org/docs/current/static/libpq-ssl.html http://www.postgresql.org/docs/current/static/libpq-connect.html#LIBPQ-PARAMKEYWORDS http://www.postgresql.org/docs/current/static/libpq-envars.html Connection parameters are "sslcert" and "sslkey", environment variables "PGSSLCERT" and "PGSSLKEY". You can also specify parameters in your .pg_service.conf. Regards, Christoph -- Spare Space -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
Re: [HACKERS] pthread portability
## Alvaro Herrera (alvhe...@2ndquadrant.com): > > The below diff fixes one problem: you can't compare pthread_t values > > directly. Only the function pthread_equal(3) is defined. Direct > > comparison usually works because most implementations define pthread_t > > as an integer type. > > So is there a platform where this assumption doesn't hold? E.g. FreeBSD has "typedef struct pthread *pthread_t;" with a non-trivial "struct pthread". Regards, Christoph -- Spare Space -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
Re: [HACKERS] 9.4 documentation: duplicate paragraph in logical decoding example
## Andres Freund (and...@2ndquadrant.com):
Care to submit a patch for it Christoph?
There it is.
Regards,
Christoph
--
Spare Space
diff --git a/doc/src/sgml/logicaldecoding.sgml b/doc/src/sgml/logicaldecoding.sgml
index 41b63b4..6c3707c 100644
--- a/doc/src/sgml/logicaldecoding.sgml
+++ b/doc/src/sgml/logicaldecoding.sgml
@@ -114,7 +114,7 @@ postgres=# SELECT * FROM pg_logical_slot_peek_changes('regression_slot', NULL, N
0/16E0B90 | 690 | COMMIT 690
(3 rows)
-postgres=# -- You can also peek ahead in the change stream without consuming changes
+postgres=# -- The next call to pg_logical_slot_peek_changes() returns the same changes again
postgres=# SELECT * FROM pg_logical_slot_peek_changes('regression_slot', NULL, NULL);
location | xid | data
---+-+---
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
[HACKERS] 9.4 documentation: duplicate paragraph in logical decoding example
Hi,
while reading the logical decoding docs, I came across a duplicated
paragraph in doc/src/sgml/logicaldecoding.sgml - in the current
master branch, lines 108 to 115 are the same as lines 117 to 124.
I've attached a patch which removes the second instance of that
paragraph.
In case it is intended to demonstrate that the changes in the stream
were not consumed by pg_logical_slot_peek_changes(), the comment
in line 117 should be removed, or reworded like the changes have
not been consumed by the previous command, just to avoid making
it look like that paragraph had been duplicated by accident :)
Regards,
Christoph
--
Spare Space
diff --git a/doc/src/sgml/logicaldecoding.sgml b/doc/src/sgml/logicaldecoding.sgml
index a2108d6..5fa2a1e 100644
--- a/doc/src/sgml/logicaldecoding.sgml
+++ b/doc/src/sgml/logicaldecoding.sgml
@@ -114,15 +114,6 @@ postgres=# SELECT * FROM pg_logical_slot_peek_changes('regression_slot', NULL, N
0/16E0B90 | 690 | COMMIT 690
(3 rows)
-postgres=# -- You can also peek ahead in the change stream without consuming changes
-postgres=# SELECT * FROM pg_logical_slot_peek_changes('regression_slot', NULL, NULL);
- location | xid | data
+-+---
- 0/16E09C0 | 690 | BEGIN 690
- 0/16E09C0 | 690 | table public.data: INSERT: id[integer]:3 data[text]:'3'
- 0/16E0B90 | 690 | COMMIT 690
-(3 rows)
-
postgres=# -- options can be passed to output plugin, to influence the formatting
postgres=# SELECT * FROM pg_logical_slot_peek_changes('regression_slot', NULL, NULL, 'include-timestamp', 'on');
location | xid | data
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
Re: [HACKERS] detecting binary backup in progress
## Joe Conway (m...@joeconway.com): However there is a period of time after pg_start_backup() is first executed to when it completes, during which backup_label file does not exist yet, but the backup has essentially been started. Is there any way to detect this state? When I did some research on the very same question just a few weeks ago, I settled for external locks (lockfile, pg_advisory_lock(), ..., depending on your exact situation) around the backup-taking code. Regards, Christoph -- Spare Space -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
