Re: The contents of the pg_timezone_names view bring some surprises

2021-05-19 Thread Bryn Llewellyn
> t...@sss.pgh.pa.us wrote: > >> david.g.johns...@gmail.com wrote: >> >>> b...@yugabyte.com wrote: >>> >>> Am I missing an essential clue to resolving what seems to me to be a >>> paradox? Or am I seeing two kinds of bug? >> >> >> You are missing the materi

Re: pgbackrest - hiding the encryption password

2021-05-19 Thread David Steele
On 5/19/21 2:48 PM, Ron wrote: On 5/19/21 1:34 PM, David Steele wrote: On 5/19/21 1:49 PM, Ron wrote: Currently on our RHEL 7.8 system, /etc/pgbackrest.conf is root:root and 633 perms.  Normally, that's ok, but is a horrible idea when it's a plaintext file, and stores the pgbackrest encrypti

Re: pgbackrest - hiding the encryption password

2021-05-19 Thread Ron
On 5/19/21 1:34 PM, David Steele wrote: On 5/19/21 1:49 PM, Ron wrote: Currently on our RHEL 7.8 system, /etc/pgbackrest.conf is root:root and 633 perms.  Normally, that's ok, but is a horrible idea when it's a plaintext file, and stores the pgbackrest encryption password. Would pgbackrest

Re: pgbackrest - hiding the encryption password

2021-05-19 Thread Ron
On 5/19/21 1:34 PM, David Steele wrote: On 5/19/21 1:49 PM, Ron wrote: Currently on our RHEL 7.8 system, /etc/pgbackrest.conf is root:root and 633 perms.  Normally, that's ok, but is a horrible idea when it's a plaintext file, and stores the pgbackrest encryption password. Would pgbackrest

Re: pgbackrest - hiding the encryption password

2021-05-19 Thread Ron
On 5/19/21 1:33 PM, Stephen Frost wrote: Greetings, * Ron (ronljohnso...@gmail.com) wrote: Currently on our RHEL 7.8 system, /etc/pgbackrest.conf is root:root and 633 perms.  Normally, that's ok, but is a horrible idea when it's a plaintext file, and stores the pgbackrest encryption password.

Re: pgbackrest - hiding the encryption password

2021-05-19 Thread David Steele
On 5/19/21 1:49 PM, Ron wrote: Currently on our RHEL 7.8 system, /etc/pgbackrest.conf is root:root and 633 perms.  Normally, that's ok, but is a horrible idea when it's a plaintext file, and stores the pgbackrest encryption password. Would pgbackrest (or something else) break if I change it

Question: pgp_sym_decrypt/pgp_sym_encrypt

2021-05-19 Thread atirek khare
> > Hi, > > I’m trying to use *pgcrypto* for encryption/ decryption of column from > SpringBoot Java application. The function I am using is *pgp_sym_encrypt/ > decrypt*. > > > > *Postgres Version: 12.3 * > > *E.g. * > > *insert* *into* employee *values* (1, 'Jay', '1 down str', 20, > *pgp_sym_enc

Re: pgbackrest - hiding the encryption password

2021-05-19 Thread Stephen Frost
Greetings, * Ron (ronljohnso...@gmail.com) wrote: > Currently on our RHEL 7.8 system, /etc/pgbackrest.conf is root:root and 633 > perms.  Normally, that's ok, but is a horrible idea when it's a plaintext > file, and stores the pgbackrest encryption password. > > Would pgbackrest (or something els

Re: pgbackrest info of encrypted seems broken

2021-05-19 Thread David Steele
On 5/19/21 1:42 PM, Ron wrote: On 5/19/21 12:08 PM, David Steele wrote: On 5/19/21 9:47 AM, Ron wrote: This is on Postgresql 9.6, if it matters.  Attached is a text file showing the pgbackrest version, config, backup log and "pgbackrest info" output. I followed the instructions in https:/

pgbackrest - hiding the encryption password

2021-05-19 Thread Ron
Currently on our RHEL 7.8 system, /etc/pgbackrest.conf is root:root and 633 perms.  Normally, that's ok, but is a horrible idea when it's a plaintext file, and stores the pgbackrest encryption password. Would pgbackrest (or something else) break if I change it to postgres:postgres 600 perms

Re: pgbackrest info of encrypted seems broken

2021-05-19 Thread Ron
On 5/19/21 12:08 PM, David Steele wrote: On 5/19/21 9:47 AM, Ron wrote: This is on Postgresql 9.6, if it matters.  Attached is a text file showing the pgbackrest version, config, backup log and "pgbackrest info" output. I followed the instructions in https://pgbackrest.org/user-guide.html#

Re: pgbackrest info of encrypted seems broken

2021-05-19 Thread David Steele
On 5/19/21 9:47 AM, Ron wrote: This is on Postgresql 9.6, if it matters.  Attached is a text file showing the pgbackrest version, config, backup log and "pgbackrest info" output. I followed the instructions in https://pgbackrest.org/user-guide.html#quickstart/configure-encryption, and succ

回复: [External] Re: PG 10 experience different user execute same sql get different access plan

2021-05-19 Thread Zhiyu ZY13 Xu
Hi Tom Thanks for your quick response. I check the table ddl. There is no row-level security turn on. There are 2 tables. dcg.brick_base_ebrThis table is partition table. And have trigger define on the table. dcg.brick_shipmentThis is very simple and normal table. I attach

Re: PG 10 experience different user execute same sql get different access plan

2021-05-19 Thread Tom Lane
Zhiyu ZY13 Xu writes: > I experience a PG optimizer problem. Different user query with same SQL at > same time. But get different access plan. If you've got row-level security turned on for that table, it could explain results like this. RLS limits the planner's ability to see statistics, whi

Re: The contents of the pg_timezone_names view bring some surprises

2021-05-19 Thread Adrian Klaver
On 5/18/21 11:31 PM, Bryn Llewellyn wrote: Some time zones have abbreviations that are identical to their names. This query: Here’s what seems to me to be a closely related dilemma. I’d thought that an abbrev uniquely specified the utc_offset. But this test shows that it doesn’t: with   v1

Re: The contents of the pg_timezone_names view bring some surprises

2021-05-19 Thread Tom Lane
"David G. Johnston" writes: > On Tuesday, May 18, 2021, Bryn Llewellyn wrote: >> Am I missing an essential clue to resolving what seems to me to be a >> paradox? Or am I seeing two kinds of bug? > You are missing the material in appendix B.4 > https://www.postgresql.org/docs/current/datetime-con

pgbackrest info of encrypted seems broken

2021-05-19 Thread Ron
This is on Postgresql 9.6, if it matters.  Attached is a text file showing the pgbackrest version, config, backup log and "pgbackrest info" output. I followed the instructions in https://pgbackrest.org/user-guide.html#quickstart/configure-encryption, and successfully ran these commands befor

Re: PgAdmin4 - 'NoneType' object has no attribute 'value'

2021-05-19 Thread Adrian Klaver
On 5/19/21 2:42 AM, Derek van den Nieuwenhuijzen wrote: Hi Postgress, I used to have a functioning PostgreSQL database, but upon reinstalling due to computer issues, I am now getting this error after launching: Traceback (most recent call last):   File "C:\Program Files\PostgreSQL\12\pgAdmin

Re: logical replication initial copy and WAL generation

2021-05-19 Thread Radoslav Nedyalkov
We have wal_log_hints = off. Then I thought hint bits are never WAL logged. Or am I missing the part - they are, upon first read ? Thanks again Rado On Wed, May 19, 2021 at 3:56 PM Laurenz Albe wrote: > On Wed, 2021-05-19 at 14:16 +0300, Radoslav Nedyalkov wrote: > > Hello Forum, > > I know it

Re: logical replication initial copy and WAL generation

2021-05-19 Thread Laurenz Albe
On Wed, 2021-05-19 at 14:16 +0300, Radoslav Nedyalkov wrote: > Hello Forum, > I know it sounds weird but we have faced it a couple of times already and > have no idea. > We're trying to establish logical replication from RDS(10.9) to RDS(12.5). > We're adding tables to the publication one by one.

logical replication initial copy and WAL generation

2021-05-19 Thread Radoslav Nedyalkov
Hello Forum, I know it sounds weird but we have faced it a couple of times already and have no idea. We're trying to establish logical replication from RDS(10.9) to RDS(12.5). We're adding tables to the publication one by one. During the initial copy for some tables we experience huge WAL generatio

Re: Plan for exclusive backup method

2021-05-19 Thread Magnus Hagander
On Wed, May 19, 2021 at 11:58 AM MEERA wrote: > > Hi team, > > https://www.postgresql.org/docs/12/continuous-archiving.html > > It is mentioned here that exclusive backup method is deprecated and should be > avoided. it is now recommended that all users upgrade their scripts to use > non-exclusi

PG 10 experience different user execute same sql get different access plan

2021-05-19 Thread Zhiyu ZY13 Xu
Hi Admin support I experience a PG optimizer problem. Different user query with same SQL at same time. But get different access plan. On the test env: PG 10.3 env. User: ccfuser. This user is DB owner. It will get result within 3 second. The totally cost is : 99672 User: a_ap

Plan for exclusive backup method

2021-05-19 Thread MEERA
Hi team, https://www.postgresql.org/docs/12/continuous-archiving.html It is mentioned here that exclusive backup method is deprecated and should be avoided. it is now recommended that all users upgrade their scripts to use non-exclusive backups. Does this mean select pg_start_backup('label', fal

PgAdmin4 - 'NoneType' object has no attribute 'value'

2021-05-19 Thread Derek van den Nieuwenhuijzen
Hi Postgress, I used to have a functioning PostgreSQL database, but upon reinstalling due to computer issues, I am now getting this error after launching: Traceback (most recent call last): File "C:\Program Files\PostgreSQL\12\pgAdmin 4\web\pgAdmin4.py", line 98, in app = create_app()

Re: The contents of the pg_timezone_names view bring some surprises

2021-05-19 Thread David G. Johnston
On Tuesday, May 18, 2021, Bryn Llewellyn wrote: > Some time zones have abbreviations that are identical to their names. This > query: > > Am I missing an essential clue to resolving what seems to me to be a > paradox? Or am I seeing two kinds of bug? > > You are missing the material in appendix B