Re: [PATCH] Absolute passwordfile path

Yes, I've resent it to pgpool-hack...@pgpool.net Sorry for the noise ср, 7 серп. 2019 о 09:18 Amit Langote пише: > Hello, > > On Wed, Aug 7, 2019 at 3:05 PM Danylo Hlynskyi > wrote: > > > > The pool_passwd option [1] is specified relative to config file. But for > g

Fwd: [PATCH] Absolute passwordfile path

The pool_passwd option [1] is specified relative to config file. But for greater flexibility absolute path should be accepted as well. If pool_passwd option starts with /, let's treat it as absolute path. Otherwise, it is treated as relative path. Patch attached. Original author - Derek Kulinski

Re: Unix socket dir, an idea

``` Thanks again for reading this! сб, 30 бер. 2019 о 02:40 Tom Lane пише: > Danylo Hlynskyi writes: > > The problem (as I see it) is that everybody would like to move `/tmp` > > socket dir to `/var/run`, or even `/var/run/postgresql` (or even > > `/run/postgresql`), but com

Unix socket dir, an idea

Before writing a patch, I'd like to hear discussion first. I've searched archives first and read following previous discussions on this topic: - https://www.postgresql.org/message-id/4FCF6040.5030408%40redhat.com - https://www.postgresql.org/message-id/14899.974513046%40sss.pgh.pa.us The problem

[FEATURE REQUEST] Encrypted indexes over encrypted data

Hi! Haven't found discussions on possible ways to encrypt indexes. Let's start! The problem == I'd like to encrypt some columns (first name, last name, SSN, etc...) in a nondeterministic way. This can be done using `pg_crypto`, but then I loose full-text-search (and any other indexing)