RE: Monitor Postgres database status on Docker

Hi Fan Liu, I am able to make the connection to the Postgres database created in docker container via psql from postgres10 client but not able to connect through pg_isready. psql -c 'select count (*) from pg_stat_activity' -h localhost -p 5432 -U postgres -W Password for user postgres: count

Re: pg12 rc1 on CentOS8 depend python2

Thank you for your reply! Even if I don't need to install plpythonu, RPM package includes "CONFIGURE = --with-python". Therefore I think that I need to install python2 when RPM install. Is my understanding correct? Best Regards. Keisuke Kuroda 2019年9月27日(金) 13:03 Adrian Klaver : > On 9/26/19

Re: pg12 rc1 on CentOS8 depend python2

On 9/26/19 6:50 PM, keisuke kuroda wrote: Hi. I tried to install PostgreSQL12 RC1 on CentOS8. # dnf install postgresql12-server postgresql12-contrib ===  Package                           Arch        

Re: managing primary key conflicts while restoring data to table with existing data

Krishnakant Mane writes: >> You might think about adding the new UUID column and use the existing >> primary key to inform the updates in dependent tables. Then remove the >> old PK  column and constraint followed by promoting the UUID to >> primary key. This could be safely scripted and applied

Re: "Failed to connect to Postgres database"

Hi, On Thu, 2019-09-26 at 16:21 +0200, Marco Ippolito wrote: > > db: > type: postgres > datasource: host=localhost port=5433 user=fabmnet_admin > password=password dbname=fabmnetdb sslmode=verify-full > > > (base) marco@pc:~/fabric/fabric-ca$ fabric-ca-server start -b >

pg12 rc1 on CentOS8 depend python2

Hi. I tried to install PostgreSQL12 RC1 on CentOS8. # dnf install postgresql12-server postgresql12-contrib === Package ArchVersion

Re: pg_get_triggerdef does not use the schema qualified procedure name

AJ Welch writes: > I noticed that pg_get_triggerdef doesn't seem to use the schema qualified > name of procedures/functions. Is it supposed to? Is there a way to get it > to? Generally the policy of such functions is to schema-qualify names that wouldn't be found in the current search_path. So

pg_get_triggerdef does not use the schema qualified procedure name

Hi, I noticed that pg_get_triggerdef doesn't seem to use the schema qualified name of procedures/functions. Is it supposed to? Is there a way to get it to? z1h=# \x auto Expanded display is used automatically. z1h=# select tg.tgname "name", nsp.nspname "schema", cls.relname table_name,

Re: row_to_json white space

On 9/26/19 11:54 AM, Mark Lybarger wrote: Ccing the list so folks know the problem is solved. Problem is on my end.  My tool was showing the space removed and infact it wasn't.  Copy paste from dbeaver to notepad++ shows the spaces are preserved. On Thu, Sep 26, 2019 at 2:49 PM Adrian

Re: "Failed to connect to Postgres database"

On 9/26/19 10:10 AM, Marco Ippolito wrote: Hi Adrian, I removed the previous fabmentdb and created a new one whose owner is postgres: (base) postgres@pc:/usr/local/pgsql$ psql --cluster 11/fabmnet psql (11.5 (Ubuntu 11.5-1.pgdg18.04+1)) Type "help" for help. postgres=# \l                  

Re: row_to_json white space

On 9/26/19 10:54 AM, Mark Lybarger wrote: Hi, The row_to_json seems to strip white space: select ROW_to_json(q) from (select 'foo        a   bar' as TEST) q; any help on how to preserve? Like Rob I do not see it: test=# select version(); version

Re: row_to_json white space

On 9/26/19 11:54 AM, Mark Lybarger wrote: select ROW_to_json(q) from (select 'foo        a   bar' as TEST) q; Not here postgres=# select ROW_to_json(q) from (select 'foo    a bar' as TEST) q;   row_to_json ---  {"test":"foo    a   bar"} (1 row)

row_to_json white space

Hi, The row_to_json seems to strip white space: select ROW_to_json(q) from (select 'fooa bar' as TEST) q; any help on how to preserve? Thanks! -mark-

Re: managing primary key conflicts while restoring data to table with existing data

On 26/09/19 6:53 PM, Rob Sargent wrote: >   > > On Sep 26, 2019, at 12:27 AM, Krishnakant Mane > wrote: > >> >> On 26/09/19 12:03 AM, Adrian Klaver wrote: >>> On 9/25/19 8:04 AM, Rob Sargent wrote: On Sep 25, 2019, at 8:24 AM, Krishnakant Mane >>>

Re: "Failed to connect to Postgres database"

Hi Adrian, I removed the previous fabmentdb and created a new one whose owner is postgres: (base) postgres@pc:/usr/local/pgsql$ psql --cluster 11/fabmnet psql (11.5 (Ubuntu 11.5-1.pgdg18.04+1)) Type "help" for help. postgres=# \l List of databases Name|

Re: managing primary key conflicts while restoring data to table with existing data

-- Regards, Krishnakant Mane, Project Founder and Leader, GNUKhata //(Opensource Accounting, Billing and Inventory Management Software)// You might think about adding the new UUID column and use the existing primary key to inform the updates in dependent tables. Then

Re: updating sequence value for column 'serial'

On 9/25/19 10:12 PM, Matthias Apitz wrote: El día miércoles, septiembre 25, 2019 a las 07:42:11a. m. -0700, Adrian Klaver escribió: sisis$# DECLARE sisis$#maxikatkey integer := ( select max(katkey) from titel_daten ); sisis$#result integer := 1; sisis$# BEGIN sisis$#maxikatkey :=

Re: "Failed to connect to Postgres database"

On 9/26/19 7:21 AM, Marco Ippolito wrote: In order to restart from a clean situation and configuration, I removed the previous fabric-ca folder, created a new one, and then initiated the fabric-ca-server. With the default SQLite everything seem working fine. But one I try to use the

Re: could not accept SSL connection: sslv3 alert bad certificate

On 9/26/19 1:10 AM, Marco Ippolito wrote: Hi Adrian, putting in /fabric/fabric-ca/fabric-ca-server-config.yaml : db:   type: postgres   datasource: host=localhost port=5433 user=fabmnet_admin password=fabmnet1971 dbname=fabmnetdb sslmode=verify-ca and the corresponding portion of the

Re: Operator is not unique

On 9/25/19 1:14 PM, PegoraroF10 wrote: format_type format_type castfunccastcontext castmethod bigint smallint714 a f bigint integer 480 a f bigint real652 i f bigint double precision482 i f bigint

"Failed to connect to Postgres database"

In order to restart from a clean situation and configuration, I removed the previous fabric-ca folder, created a new one, and then initiated the fabric-ca-server. With the default SQLite everything seem working fine. But one I try to use the PostgreSQL-11 db I created before, errors appear:

Re: managing primary key conflicts while restoring data to table with existing data

> On Sep 26, 2019, at 7:44 AM, Krishnakant Mane wrote: > > >> On 26/09/19 6:53 PM, Rob Sargent wrote: >> >> >> On Sep 26, 2019, at 12:27 AM, Krishnakant Mane wrote: >> >>> On 26/09/19 12:03 AM, Adrian Klaver wrote: > On 9/25/19 8:04 AM, Rob Sargent wrote: > > >

Re: Use of ?get diagnostics'?

On 9/25/19 10:44 PM, Thiemo Kellner wrote: Hello Adrian Quoting Adrian Klaver : To get above I believe you will need to use GET CURRENT DIAGNOSTICS PG_CONTEXT: I actually use "get stacked diagnostics" to retrieve the exception place. And it works. I am not sure why I did no see it. GET [

Re: managing primary key conflicts while restoring data to table with existing data

> On Sep 26, 2019, at 12:27 AM, Krishnakant Mane wrote: > > >> On 26/09/19 12:03 AM, Adrian Klaver wrote: >>> On 9/25/19 8:04 AM, Rob Sargent wrote: >>> >>> >>> On Sep 25, 2019, at 8:24 AM, Krishnakant Mane >> > wrote: >>> > On 25/09/19 7:50 PM,

Re: managing primary key conflicts while restoring data to table with existing data

On 26/09/19 12:03 AM, Adrian Klaver wrote: > On 9/25/19 8:04 AM, Rob Sargent wrote: >> >> >> On Sep 25, 2019, at 8:24 AM, Krishnakant Mane > > wrote: >> >>> >>> On 25/09/19 7:50 PM, Adrian Klaver wrote: On 9/25/19 12:15 AM, Krishnakant Mane wrote: > Hello all,

Re: could not accept SSL connection: sslv3 alert bad certificate

Affer removing the previous cert and key files, I started again the fabric-ca server discovering that new cert and key files were created: (base) marco@pc:~/fabric/fabric-ca$ fabric-ca-server start -b admin:adminpw 2019/09/26 11:56:18 [INFO] Configuration file location:

Logical replicatino from standby

Hi. Will the feature described here (Minimal logical decoding on standbys): https://www.postgresql.org/message-id/flat/20181212204154.nsxf3gzqv3gesl32%40alap3.anarazel.de make it possible to do

Re: could not accept SSL connection: sslv3 alert bad certificate

Thanks Martin. I need to check these important aspects as well. What do you mean as "disable hardcoded BCCSP Provider"? Marco Il giorno gio 26 set 2019 alle ore 00:43 Martin Gainty ha scritto: > Hi Marco > > not necessarily with PG but with all other servers i secure when i see > that error >

Re: could not accept SSL connection: sslv3 alert bad certificate

Hi Adrian, putting in /fabric/fabric-ca/fabric-ca-server-config.yaml : db: type: postgres datasource: host=localhost port=5433 user=fabmnet_admin password=fabmnet1971 dbname=fabmnetdb sslmode=verify-ca this is the result: (base) marco@pc:~/fabric/fabric-ca$ fabric-ca-server start -b