Re: Copy json from couchbase to postgres

On Mon, Oct 26, 2020 at 1:10 PM Rushikesh socha wrote: > Any suggestions on copying .json which is exported from couchbase > using cbexport json. I used copy command but most of them are throwing > error. > > pgdocstore=# copy schaname.tablename from 'path/filename.json'; > ERROR: invalid input

Copy json from couchbase to postgres

Any suggestions on copying .json which is exported from couchbase using cbexport json. I used copy command but most of them are throwing error. pgdocstore=# copy schaname.tablename from 'path/filename.json'; ERROR: invalid input syntax for type json DETAIL: Token "H" is invalid.

Re: postgis update wants to install postgresql-13

On 10/26/20 6:34 AM, Hu Bert wrote: Hi there, i hope i'm right here... i just wanted to install some debian updates (buster) and saw that there are postgres/postgis updates as well. Currently installed: postgis 3.0.2+dfsg-2.pgdg100+1 postgis-doc

Re: Feature Requests

On Sun, Oct 25, 2020 at 10:26 AM Nikolai Lusan wrote: > Hi, > > I was wondering where I can see open feature requests. One I would like > to see is multi-master replication ... I did find a 2016 request that > was marked as "planned", but to the best of my knowledge it hasn't made > production

Re: postgres materialized view refresh performance

> On Oct 26, 2020, at 10:45 AM, Ayub M wrote: > > It's a simple sequential scan plan of one line, just reading the base table > sequentially. Well, unless I have misunderstood you, the materialized view is basically just "select * from some_other_table”, the number of records in the

postgis update wants to install postgresql-13

Hi there, i hope i'm right here... i just wanted to install some debian updates (buster) and saw that there are postgres/postgis updates as well. Currently installed: postgis 3.0.2+dfsg-2.pgdg100+1 postgis-doc 3.0.2+dfsg-2.pgdg100+1 postgresql-12

Re: postgres materialized view refresh performance

It's a simple sequential scan plan of one line, just reading the base table sequentially. On Mon, Oct 26, 2020, 9:21 AM Philip Semanchuk wrote: > > > > On Oct 25, 2020, at 10:52 PM, Ayub M wrote: > > > > Thank you both. > > > > As for the mview refresh taking long -- > > • The mview gets

PG Crashed at CheckExprStillValid with state == NULL (PG 11.2)

Hi: The call stack is below: #0 0x7fdecbe924eb in raise () from /lib64/libpthread.so.0 #1 0x00886888 in . () #2 #3 0x006cb364 in ?? () #4 0x006cb2a4 in CheckExprStillValid () --> *state == NULL* #5 0x006c9563 in ExecInterpExprStillValid () #6

Re: postgres materialized view refresh performance

> On Oct 25, 2020, at 10:52 PM, Ayub M wrote: > > Thank you both. > > As for the mview refresh taking long -- > • The mview gets refreshed in a couple of mins sometimes and sometimes it > takes hours. When it runs for longer, there are no locks and no resource > shortage, the number of

facing problem in outparameters in c

Hi Team, i am facing the problem in passing the outparameters in postgres package calling by using c language.can you please help us to solve the problem.. below is way iam calling the package. snprintf(buffer, sizeof(buffer),"SELECT

Open source monitoring streaming replication

Hi Team, Is there any open source monitoring tool can we use to configure monitoring PostgreSQL Primary-Standby as a single group instead of adding servers as individual monitoring. In my case I am using repmgr for automatic failover between primary and standby. primary, standby instances are