Re: Connection type

> On Jan 18, 2018, at 4:06 PM, Enrico Pirozzi wrote: > > Hi, > > is there a way to know what kind of connection a client is doing? > (ODBC,JDBC..etc) > > I saw the pg_stat_activity view, > > > but in the application name field there no infomation about > what kind

Connection type

Hi, is there a way to know what kind of connection a client is doing? (ODBC,JDBC..etc) I saw the pg_stat_activity view, but in the application name field there no infomation about what kind of connection a client is doing. Thanks Enrico e.piro...@nbsgroup.it

Could not read block in file

This morning I got some errors from our pre-prod environment. This is running Pg 9.6.6 on CentOS 7.3. Just grepping out these errors (and obfuscating sensitive data): 2018-01-18 06:29:21 CST [11912]: [1570-1] db=abcprod,user=abcreporting2,app=PostgreSQL JDBC Driver,client=

Re: Call sql function in psql

> On Jan 18, 2018, at 9:22 AM, Abhra Kar wrote: > > Hi All, > > Please send me some info how to post directly in mailing > list,somwhow I am not able to find out the way so I am mailing here. > > Here is fine > > Present problem-- > > > >

Re: Connection type

Il 18/01/2018 17:19, Steve Atkins ha scritto: A client can voluntarily set the application_name, e.g. as part of it's connection string, to identify itself to the server, if you want to be able to identify which sort of client is connected easily. Thank you very much :) Regards Enrico

Possible hang in 10.1 with JSON query over partially indexed partitions

Version 10.1, Community version from PGDG repo OSRHEL 7.3 I may have discovered a situation in 10.1 where EXECUTEing a PREPARED statement acting on JSON data in partitioned tables hangs in an infinite loop for a particular set of data. Unfortunately, the data is proprietary, so I did

Partitioning constraints vs before-trigger

Hi all, Could anybody explain, what happens first: constraint check or before-trigger execution? I have a table, partitioned by date: CREATE TABLE foo (   unid text NOT NULL,   logtime timestamp with time zone NOT NULL,   size integer,   CONSTRAINT foo_pkey PRIMARY KEY (unid) ); -- There is

warning for subquery that references a table but not its columns

I almost got bit by this today: => select email from subscribed where email not in (select email from tracks); email --- (0 rows) => select email from subscribed where email not in (select tracks.email from tracks); ERROR: column tracks.email does not exist LINE 1: ... email from

Re: warning for subquery that references a table but not its columns

Seamus Abshere writes: > Should there be a warning for the first query that you reference "tracks" in > a subquery but don't use any columns from it? Unfortunately, outer references in subqueries are perfectly legal per SQL standard, and also often essential. If we were to

Re: Possible hang in 10.1 with JSON query over partially indexed partitions

Paul Jones writes: > I may have discovered a situation in 10.1 where EXECUTEing a PREPARED > statement acting on JSON data in partitioned tables hangs in an > infinite loop for a particular set of data. Unfortunately, the data is > proprietary, so I did the best I could below