Re: csvlog Behavior when log file missing

2019-06-03 Thread Laurenz Albe
Lesley Kimmel wrote: > I have a system where postgres seems to be randomly dying. When researching > the issue > I, of course, began looking at logs. > > I found that much of the logs were missing due to logrotate configuration on > the server. > Logs were being rotated by size and then compress

Fwd: SSL Error: Certificate verify fail

2019-06-03 Thread Richard Webb
Hi, I have completed the steps at https://www.postgresql.org/docs/current/ssl-tcp.html#SSL-CLIENT-CERTIFICATES Specifically: To create a server certificate whose identity can be validated by clients, first create a certificate signing request (CSR) and a public/private key file: openssl req -

Re: Questions about btree_gin vs btree_gist for low cardinality columns

2019-06-03 Thread Jeff Janes
On Sun, Jun 2, 2019 at 7:07 PM Tom Lane wrote: > Jeff Janes writes: > > On Fri, May 24, 2019 at 11:26 AM Jeremy Finzel > wrote: > >> I have been hoping for clearer direction from the community about > >> specifically btree_gin indexes for low cardinality columns (as well as > low > >> cardinali

csvlog Behavior when log file missing

2019-06-03 Thread Lesley Kimmel
Hi all; I have a system where postgres seems to be randomly dying. When researching the issue I, of course, began looking at logs. I found that much of the logs were missing due to logrotate configuration on the server. Logs were being rotated by size and then compressed. Because of this, the fir

Re: One way replication in PostgreSQL

2019-06-03 Thread Frank Alberto Rodriguez
You could use FDW to replicate what you need to an external server from the provider/primary/master to the subscriber/secondary/slaveUsing triggers on the master tables that you want to replicate, you can execute the insert/update/delete actions on the secondary tables through the FDW.With this app

Re: Questions about btree_gin vs btree_gist for low cardinality columns

2019-06-03 Thread Peter Geoghegan
On Sun, Jun 2, 2019 at 4:07 PM Tom Lane wrote: > Anyway, I said to Jeremy in the hallway that it might not be that > hard to bolt IOS support onto GIN for cases where the opclass is > a non-subdividing one, but after looking at the code I'm less sure > about that. GIN hasn't even got an "amgettup

Requirement PA-DSS 1.1.4

2019-06-03 Thread Jan Bilek
Hi, We've build a Payments Authorisation system (Box solution) on Postgresql database and now we are hitting following issue with our PA:DSS audit - requirement PA-DSS 1.1.4: <> 1.1.4 Securely delete any track data (from the magnetic stripe or equivalent data contained on a chip), card verific

Re: Cause: org.postgresql.util.PSQLException: ERROR: could not resize shared memory segment "/PostgreSQL.1946998112" to 8388608 bytes: No space left on device

2019-06-03 Thread Thomas Munro
On Mon, Jun 3, 2019 at 5:56 AM Daulat Ram wrote: > Cause: org.postgresql.util.PSQLException: ERROR: could not resize shared > memory segment "/PostgreSQL.1946998112" to 8388608 bytes: No space left on > device > shm on /dev/shm type tmpfs > (rw,context="system_u:object_r:container_file_t:s0:c1

Re: One way replication in PostgreSQL

2019-06-03 Thread Fabio Pardi
Hi, On 6/3/19 6:00 PM, PALAYRET Jacques wrote: > Hello, > > If, for security reasons, I can't create a connection or a flow from > subscriber/secundary/slave towards provider/primary/master, witch > replication systems can I use ? > To perform replication, you need some form of connectivity be

Re: One way replication in PostgreSQL

2019-06-03 Thread Stephen Frost
Greetings, * PALAYRET Jacques (jacques.palay...@meteo.fr) wrote: > If, for security reasons, I can't create a connection or a flow from > subscriber/secundary/slave towards provider/primary/master, witch replication > systems can I use ? The simplest approach might be to use WAL shipping with

One way replication in PostgreSQL

2019-06-03 Thread PALAYRET Jacques
Hello, If, for security reasons, I can't create a connection or a flow from subscriber/secundary/slave towards provider/primary/master, witch replication systems can I use ? If possible, I would prefer partial replication (only some tables) to full base replication (all instances). Do trig

Re: Postgresql backup via LVM snapshot?

2019-06-03 Thread Fabio Ugo Venchiarutti
Are you trying to fit the postgres backups in some overarching LVM-based backup scheme you're already running or is this from scratch? With the possible exception of rsync's deltas & hardlink trickeries between full backups, I personally don't see a point in using a block/file-level copy for

Re: Postgresql backup via LVM snapshot?

2019-06-03 Thread Bruno Lavoie
Hi, I suggest you to take a serious look at ZFS: https://zfsonlinux.org/ With simply a few commands, mainly zpool and zfs, you can manage everything in one stack: * encryption: new in 0.8.0 * compression: with lz4, it's very lightweitgh with practically no impact on cpu * snapshots: it

RE: Questions about btree_gin vs btree_gist for low cardinality columns

2019-06-03 Thread Steven Winfield
> In the case of a single column with a small set of distinct values over a > large set of rows, how would a Bloom filter be preferable to, say, a GIN > index on an integer value?  I don't think it would - it's probably better suited to the multi-column case you described previously. > I have

Re: Questions about btree_gin vs btree_gist for low cardinality columns

2019-06-03 Thread Morris de Oryx
I didn't notice Bloom filters in the conversation so far, and have been waiting for *years* for a good excuse to use a Bloom filter. I ran into them years back in Splunk, which is a distributed log store. There's an obvious benefit to a probabalistic tool like a Bloom filter there since remote look

CREATE DATABASE ... TEMPLATE ... vs checksums

2019-06-03 Thread Karsten Hilbert
The application I am working on is doing database upgrades by cloning the previous release into a new database by means of CREATE DATABASE new_one TEMPLATE old_one ...; (health care, extremely conservative, contingency: can switch back to still existing old database with old client at any

Cause: org.postgresql.util.PSQLException: ERROR: could not resize shared memory segment "/PostgreSQL.1946998112" to 8388608 bytes: No space left on device

2019-06-03 Thread Daulat Ram
Hello team, I'm getting below error while accessing postgres11 database. Please suggest the solution for this issue. Cause: org.postgresql.util.PSQLException: ERROR: could not resize shared memory segment "/PostgreSQL.1946998112" to 8388608 bytes: No space left on device at com.caucho.el