ey" PRIMARY KEY, btree (process_instance_id)
"*fki_conv_konotor_user_user_id*" btree (user_id) WITH (fillfactor='70')
Regards, Amarendra
On Fri, May 8, 2020 at 12:01 AM Virendra Kumar wrote:
> Sending table structure with indexes might help little further in
>
ers: shared hit=43065
Planning time: 0.455 ms
Execution time: 85.830 ms
On Thu, May 7, 2020 at 11:19 PM Amarendra Konda
wrote:
> Hi David,
>
> Thanks for the reply.This has optimized number of rows.
>
> Can you please explain, why it is getting more columns in output, even
86 ms
(20 rows)
On Thu, May 7, 2020 at 9:17 PM David G. Johnston
wrote:
> On Thu, May 7, 2020 at 7:40 AM Adrian Klaver
> wrote:
>
>> On 5/7/20 4:19 AM, Amarendra Konda wrote:
>> > Hi,
>> >
>> > PostgreSQL version : PostgreSQL 9.6.2 on x86_64-pc-l
Index Cond: ((pa.process_instance_id = ANY
('{137074941043913,164357609323111}'::bigint[])) AND (pa.app_id =
'126502930200650'::bigint) AND (m.created > '1970-01-01
00:00:00'::timestamp without time
zone))
Buffers: shared hit=55
Planning time: 1.710 ms
Executio
Hi,
PostgreSQL version : PostgreSQL 9.6.2 on x86_64-pc-linux-gnu, compiled by
gcc (GCC) 4.8.3 20140911 (Red Hat 4.8.3-9), 64-bit
We have noticed huge difference interms of execution plan ( response time)
, When we pass the direct values Vs inner query to IN clause.
High level details of the us
to do with the Tomcat server. On test server, We were seeing around 45 K +
queries with very minimal load.
Regards, Amarendra
On Mon, Oct 14, 2019 at 7:45 PM Adrian Klaver
wrote:
> On 10/13/19 10:24 PM, Amarendra Konda wrote:
> > Hi Adrian,
> >
> > Thanks a lot for the resp
zone" .
Regards, Amarendra
On Fri, Oct 11, 2019 at 7:33 PM Adrian Klaver
wrote:
> On 10/11/19 4:49 AM, Amarendra Konda wrote:
> > Hi,
> >
> > In our test environment, it was observed that there are too many queries
> > were getting fired to the database server,
Hi,
In our test environment, it was observed that there are too many queries
were getting fired to the database server, even though they are not part of
the SQL query execution.
And the number of queries that were coming to server are very high. Can you
please suggest on how to avoid these querie
