Re: When are Predicate Locks Freed

2019-12-12 Thread Thomas Munro
On Fri, Dec 13, 2019 at 5:00 AM Dave Halter wrote: > I have worked quite a bit with serializable transactions. I'm trying > to understand when predicate locks are freed. I read the whole > README-SSI [1], but I'm still not sure when a predicate lock gets > dropped. > > What I learned from that REA

Re: Backup and Restore

2019-12-12 Thread Andreas Kretschmer
Am 12.12.19 um 16:12 schrieb Dor Ben Dov: What is the most common used back and restore solution for postgres ? most of our customers are using Barman, which is not a surprise since it is developed by us ;-) Regards, Andreas -- 2ndQuadrant - The PostgreSQL Support Company. www.2ndQuadra

When are Predicate Locks Freed

2019-12-12 Thread Dave Halter
Hello PostgreSQL Community I have worked quite a bit with serializable transactions. I'm trying to understand when predicate locks are freed. I read the whole README-SSI [1], but I'm still not sure when a predicate lock gets dropped. What I learned from that README is that predicate locks are not

Re: Backup and Restore

2019-12-12 Thread Grigory Smolkin
Hello! I would recommend to look at pg_probackup: https://github.com/postgrespro/pg_probackup On 12/12/19 6:12 PM, Dor Ben Dov wrote: Hi, What is the most common used back and restore solution for postgres ? Which one are you using ? Regards, Dor *This email and the information contained

Re: Backup and Restore

2019-12-12 Thread Adrian Klaver
On 12/12/19 7:12 AM, Dor Ben Dov wrote: Hi, What is the most common used back and restore solution for postgres ? I would say it goes from pg_dump/pg_restore for smaller databases to some form of replication for larger. Which one are you using ? I use pg_dump/pg_restore and have started

Backup and Restore

2019-12-12 Thread Dor Ben Dov
Hi, What is the most common used back and restore solution for postgres ? Which one are you using ? Regards, Dor This email and the information contained herein is proprietary and confidential and subject to the Amdocs Email Terms of Service, which you may review at https://www.amdocs.com/abou

Async_Notify

2019-12-12 Thread Арсен Арутюнян
Hello! I wrote my extension for PG and am trying to run Async_Notify from it. But messages come very late! Sometimes only after I execute the notify command from the shell. What am I doing wrong? How to use Async_Notify correctly.   -- Арсен Арутюнян

Re: Logical replication DNS cache

2019-12-12 Thread Peter Eisentraut
On 2019-12-12 01:37, Mike Lissner wrote: I've got a server at example.com that currently publishes logical replication to a server in AWS RDS. I plan to move the server at example.com so that it has a new IP address (but same domain name). I'm curious

Re: Encoding/collation question

2019-12-12 Thread Rich Shepard
On Thu, 12 Dec 2019, Andrew Gierth wrote: Note that it's perfectly fine to use UTF8 encoding and C collation (this has the effect of sorting strings in Unicode codepoint order); this is as fast for comparisons as LATIN1/C is. Andrew, This is really useful insight. I've not thought of the rela

Re: Encoding/collation question

2019-12-12 Thread Tom Lane
Karsten Hilbert writes: > Question: is C collation expected to be future-proof / > rock-solid /stable -- like UTF8 for encoding choice -- or > could it end up like the SQL-ASCII encoding did: Yeah, we > support it, it's been in use a long time, it should work, > but, nah, one doesn't really want t

RE: PostgreSQL version compatibility with RHEL7.7

2019-12-12 Thread Deepti Sharma S
Hello Team, Can you please confirm if PostgreSQL version 11.6 is compatible with RHEL7.7? [Ericsson] DEEPTI SHARMA Specialist ITIL 2011 Foundation Certified BDGS, R&D Ericsson 3rd Floor, ASF Insignia - Block B Kings Canyon, Gwal Pahari, Gurgaon, Haryana 122 003, India

Re: Encoding/collation question

2019-12-12 Thread Karsten Hilbert
On Thu, Dec 12, 2019 at 05:03:59AM +, Andrew Gierth wrote: > Rich> I doubt that my use will notice meaningful differences. Since > Rich> there are only two or three databases in UTF8 and its collation > Rich> perhaps I'll convert those to LATIN1 and C. > > Note that it's perfectly fine to u