RE: How to double-quote a double quoted identifier?

2020-06-15 Thread Edson Richter
De: Tom Lane Enviado: segunda-feira, 15 de junho de 2020 22:24 Para: Edson Richter Cc: pgsql-general Assunto: Re: How to double-quote a double quoted identifier? Edson Richter writes: > How do I remote execute que following command: > CREATE EXTENSION "uuid-ossp" > SCHEMA public >

Re: How to double-quote a double quoted identifier?

2020-06-15 Thread Tom Lane
Edson Richter writes: > How do I remote execute que following command: > CREATE EXTENSION "uuid-ossp" > SCHEMA public > VERSION "1.1"; > I'm using PostgreSQL 9.6, Linux x64, and bash. > I've tried the following: > ssh -l postgres -2 -C -p 2022 192.168.0.70 "psql -h 127.0.0.1 -d test_db

How to double-quote a double quoted identifier?

2020-06-15 Thread Edson Richter
How do I remote execute que following command: CREATE EXTENSION "uuid-ossp" SCHEMA public VERSION "1.1"; I'm using PostgreSQL 9.6, Linux x64, and bash. I've tried the following: ssh -l postgres -2 -C -p 2022 192.168.0.70 "psql -h 127.0.0.1 -d test_db -p 5432 -c \"CREATE EXTENSION

Re: Something else about Redo Logs disappearing

2020-06-15 Thread Laurenz Albe
On Mon, 2020-06-15 at 19:00 +0200, Peter wrote: > And that is one of a couple of likely pitfalls I perceived when > looking at that new API. That is a property of my scripts, *not* of the non-exclusive backup API... > We could fix that, but that will then get more complicated - and > people will

Re: Should I enforce ssl/local socket use?

2020-06-15 Thread Bruce Momjian
On Sun, Jun 7, 2020 at 10:32:39AM +1000, Tim Cross wrote: > > Michel Pelletier writes: > > > Hello, > > > > I'm the author of the pgsodium cryptography library. I have a question > > about a best practice I'm thinking of enforcing. Several functions in > > pgsodium generate secrets, I want

Re: Index no longer being used, destroying and recreating it restores use.

2020-06-15 Thread Michael Lewis
On Tue, Jun 9, 2020 at 6:24 AM Koen De Groote wrote: > Right. In that case, the function I ended up with is this: > > create or replace function still_needs_backup(bool, bool) > returns BOOLEAN as $$ > BEGIN > PERFORM 1 from item where shouldbebackedup=$1 and backupperformed=$2; > IF

Re: Move configuration files with pg_upgrade

2020-06-15 Thread Bruce Momjian
On Thu, Jun 4, 2020 at 03:26:07PM -0700, Adrian Klaver wrote: > On 6/4/20 12:52 PM, Tanja Savic wrote: > > Hello, > > > > I did Postgresql upgrade from v10 to v12 using pg_upgrade (on Linux > > Ubuntu server). > > Of course i wanted settings inpg_hba.conf and postgresql.conf to keep, > > but

Re: Index no longer being used, destroying and recreating it restores use.

2020-06-15 Thread Bruce Momjian
On Tue, Jun 9, 2020 at 02:23:51PM +0200, Koen De Groote wrote: > Right. In that case, the function I ended up with is this: > > create or replace function still_needs_backup(bool, bool) > returns BOOLEAN as $$ > BEGIN                 >     PERFORM 1 from item where shouldbebackedup=$1 and

Re: Something else about Redo Logs disappearing

2020-06-15 Thread Peter
On Mon, Jun 15, 2020 at 03:19:29PM +0200, Laurenz Albe wrote: ! On Mon, 2020-06-15 at 14:50 +0200, Peter wrote: ! > ! An example: ! > ! ! > ! - Backup #1 calls "pgpre.sh" ! > ! - Backup #1 starts copying files ! > ! - Backup #2 calls "pgpre.sh". ! > ! This will cancel the first backup. ! > ! -

Re: Assigning values to a range in Pgsql and inclusive / exclusive bounds

2020-06-15 Thread Ron Clarke
Thanks for that perfect... missed the use of tstzrange() as a 'function' in the documentation. Best regards Ron On Fri, 12 Jun 2020 at 21:02, Adrian Klaver wrote: > On 6/12/20 11:45 AM, Ron Clarke wrote: > > Hi, > > > > I've got a simple problem, but I'm convinced that there must be an > >

SV: SV: pg_service.conf and client support

2020-06-15 Thread Niels Jespersen
Fra: Laurenz Albe Sendt: 15. juni 2020 15:36 Til: Niels Jespersen ; pgsql-gene...@postgresql.org Emne: Re: SV: pg_service.conf and client support On Mon, 2020-06-15 at 11:58 +, Niels Jespersen wrote: > > For your examples that means: > > - The PostgreSQL ODBC server can use pg_service.conf

Re: TOAST table size in bytes growing despite working autovacuum

2020-06-15 Thread Laurenz Albe
On Mon, 2020-06-15 at 16:42 +0300, Kristjan Mustkivi wrote: > > You should schedule down time and run a VACUUM (FULL) on that table. > > That will rewrite the table and get rid of the bloat. > > But in order to avoid the situation happening again (as it will with > the current settings), I should

Re: Mixed Locales and Upgrading

2020-06-15 Thread Don Seiler
Good morning, Back with a follow-up question to all this. I'm wondering if we shouldn't also change the locale settings for postgres/template0/template1 to match our new desires setting en_US.UTF-8 with UTF8 encoding. We haven't written anything to postgres. Some of our DB clusters have changed

RE: Getting error on

2020-06-15 Thread M Tarkeshwar Rao
Thanks for reply. Can you please suggest why this error occur? Any resource crunch on postgres server? Regards Tarkeshwar From: Ron Sent: Monday, June 15, 2020 7:17 PM To: pgsql-general@lists.postgresql.org Subject: Re: Getting error on On 6/15/20 8:43 AM, M Tarkeshwar Rao wrote: Hi all, I

Re: Getting error on

2020-06-15 Thread Ron
On 6/15/20 8:43 AM, M Tarkeshwar Rao wrote: Hi all, I have the c++ postgres client. When I restarted my client process I am getting following error on insertion. Can you please suggest why this error is coming and how to resolve it? The error hint says how to resolve it. 2020-04-17

Getting error on

2020-06-15 Thread M Tarkeshwar Rao
Hi all, I have the c++ postgres client. When I restarted my client process I am getting following error on insertion. Can you please suggest why this error is coming and how to resolve it? 2020-04-17 06:30:04.498 PRINT_DEFAULT_ERROR: Processor-DefaultCollectorGroup-0 :DRViewerPoint.cc :notify

Re: TOAST table size in bytes growing despite working autovacuum

2020-06-15 Thread Kristjan Mustkivi
On Mon, Jun 15, 2020 at 4:37 PM Laurenz Albe wrote: > > On Mon, 2020-06-15 at 13:47 +0300, Kristjan Mustkivi wrote: > > Still, pgstattuple reveals that the table size is 715MB while live > > tuple len is just 39MB and 94% of the table is vacant. I do not have > > much experience in interpreting

Re: TOAST table size in bytes growing despite working autovacuum

2020-06-15 Thread Laurenz Albe
On Mon, 2020-06-15 at 13:47 +0300, Kristjan Mustkivi wrote: > Still, pgstattuple reveals that the table size is 715MB while live > tuple len is just 39MB and 94% of the table is vacant. I do not have > much experience in interpreting this but it would seem that it is > still getting bloated.

Re: SV: pg_service.conf and client support

2020-06-15 Thread Laurenz Albe
On Mon, 2020-06-15 at 11:58 +, Niels Jespersen wrote: > > For your examples that means: > > - The PostgreSQL ODBC server can use pg_service.conf > > - NpgSQL cannot use the file. > > You mention that the PostgreSQL ODBC driver can use pg_service.conf. But I > cannot > find any examples om

Replication error

2020-06-15 Thread Sonam Sharma
I"m running postgres DB on docker & database replication have been enabled. After configuring repmgr not able to switch over/failover operation.DB & errors details are provided below. Please help on this. * ssh -o Batchmode=yes -q -o ConnectTimeout=10 10.0.0.76

Re: Something else about Redo Logs disappearing

2020-06-15 Thread Laurenz Albe
On Mon, 2020-06-15 at 14:50 +0200, Peter wrote: > ! An example: > ! > ! - Backup #1 calls "pgpre.sh" > ! - Backup #1 starts copying files > ! - Backup #2 calls "pgpre.sh". > ! This will cancel the first backup. > ! - Backup #1 completes copying files. > ! - Backup #1 calls "pgpost.sh". > ! It

Re: Something else about Redo Logs disappearing

2020-06-15 Thread Peter
On Mon, Jun 15, 2020 at 11:44:33AM +0200, Laurenz Albe wrote: ! On Sat, 2020-06-13 at 19:48 +0200, Peter wrote: ! > ! > 4. If, by misconfiguration and/or operator error, the backup system ! > ! > happens to start a second backup. in parallel to the first, ! > ! > then do I correctly

SV: pg_service.conf and client support

2020-06-15 Thread Niels Jespersen
-Oprindelig meddelelse- Fra: Laurenz Albe Sendt: 15. juni 2020 11:24 Til: Niels Jespersen ; pgsql-gene...@postgresql.org Emne: Re: pg_service.conf and client support On Sun, 2020-06-14 at 05:03 +, Niels Jespersen wrote: > I just found out about the pg service file. >

Re: TOAST table size in bytes growing despite working autovacuum

2020-06-15 Thread Kristjan Mustkivi
On Mon, Jun 15, 2020 at 12:17 PM Laurenz Albe wrote: > > On Mon, 2020-06-15 at 11:51 +0300, Kristjan Mustkivi wrote: > > I have a table which contains a "json" column and it gets heavily > > updated. Before introducing toast.autovacuum_vacuum_scale_factor=0.05 > > and

Re: Something else about Redo Logs disappearing

2020-06-15 Thread Laurenz Albe
On Sat, 2020-06-13 at 19:48 +0200, Peter wrote: > ! > 4. If, by misconfiguration and/or operator error, the backup system > ! > happens to start a second backup. in parallel to the first, > ! > then do I correctly assume, both backups will be rendered > ! > inconsistent while this may

Re: Oracle vs. PostgreSQL - a comment

2020-06-15 Thread Laurenz Albe
On Sun, 2020-06-14 at 09:17 -0400, Bruce Momjian wrote: > On Sat, Jun 13, 2020 at 09:27:25PM -0400, Bruce Momjian wrote: > > On Sat, Jun 13, 2020 at 05:06:37PM -0500, Ron wrote: > > > On 6/13/20 1:46 PM, Bruce Momjian wrote: > > > > On Wed, Jun 3, 2020 at 08:53:45PM +0200, Andreas Joseph Krogh

Re: pg_service.conf and client support

2020-06-15 Thread Laurenz Albe
On Sun, 2020-06-14 at 05:03 +, Niels Jespersen wrote: > I just found out about the pg service file. > https://www.postgresql.org/docs/current/libpq-pgservice.html > > I don’t know why it took me so long finding this. I have been looking for > ways to abstract physical details of data

Re: TOAST table size in bytes growing despite working autovacuum

2020-06-15 Thread Laurenz Albe
On Mon, 2020-06-15 at 11:51 +0300, Kristjan Mustkivi wrote: > Dear all, > > I have a table which contains a "json" column and it gets heavily > updated. Before introducing toast.autovacuum_vacuum_scale_factor=0.05 > and toast.autovacuum_vacuum_cost_limit=1000 this table bloated to > nearly 1TB in

TOAST table size in bytes growing despite working autovacuum

2020-06-15 Thread Kristjan Mustkivi
Dear all, I have a table which contains a "json" column and it gets heavily updated. Before introducing toast.autovacuum_vacuum_scale_factor=0.05 and toast.autovacuum_vacuum_cost_limit=1000 this table bloated to nearly 1TB in a short while. Now the n_dead_tup value is nicely under control but

Re: A query in Streaming Replication

2020-06-15 Thread Sreerama Manoj
Hello, Can anyone check this and respond please!! Thanks and regards, Manoj. On Sat, Jun 13, 2020, 20:26 Sreerama Manoj wrote: > Hello, > I use streaming replication in async mode. When master gets down, > slave will be promoted using a trigger file. During this process