Slow queries after Windows startup

2018-01-11 Thread POUSSEL, Guillaume 
Hello,

 

I’m running PostgreSQL 9.3 on Windows 7 and I’m having a performance
issue at startup. I have installed PostgreSQL as a service through Windows
installer.

The database size is 3 Go, with 120 tables.

 

Every time I try to run queries right after Windows startup, it takes a
huge amount of time.

If I restart the PostgreSQL Windows service, queries are way faster.

 

I have activated debug log and here is what I get before Windows restart:

duration: 2.000 ms  parse

duration: 3.000 ms  bind

duration: 0.000 ms  execute

And after Windows restart:

duration: 364.000 ms  parse

duration: 415.000 ms  bind

duration: 0.000 ms  execute


For information, the test query is:

SELECT t.typlen FROM pg_catalog.pg_type t, pg_catalog.pg_namespace n WHERE
t.typnamespace=n.oid AND t.typname='name' AND n.nspname='pg_catalog'

It’s not related to the query itself since other queries give the same
result (from 10x to 100x longer).

 

Here are my settings (all log and locale-related settings omitted on
purpose):


bytea_output

escape

session


checkpoint_segments

45

configuration file


client_encoding

UNICODE

session


client_min_messages

notice

session


DateStyle

ISO, DMY

session


debug_pretty_print

on

configuration file


debug_print_plan

on

configuration file


default_text_search_config

pg_catalog.french

configuration file


listen_addresses

*

configuration file


logging_collector

on

configuration file


max_connections

100

configuration file


max_stack_depth

2MB

environment variable


port

5432

configuration file


shared_buffers

128MB

configuration file


TimeZone

GMT

user

 

I run queries through JDBC driver (9.3-1100-jdbc4.jar). I know that the
issue is not related to the PC, since it give the same result on a bunch of
different computers.

 

I have two questions:

* What is the difference between restarting PostgreSQL service and
restarting the computer? Is PostgreSQL relying on some kind of OS-level
cache outside Windows service?

* How can I dig down deeper and see what’s causing PostgreSQL
slowdown?

 

Thanks in advance for your help,

BR,

 

Guillaume POUSSEL | ♠Sogeti High Tech

  [email protected]

 

 

 

 

 



smime.p7s
Description: S/MIME cryptographic signature
This message contains information that may be privileged or confidential and is 
the property of the Capgemini Group. It is intended only for the person to whom 
it is addressed. If you are not the intended recipient, you are not authorized 
to read, print, retain, copy, disseminate, distribute, or use this message or 
any part thereof. If you receive this message in error, please notify the 
sender immediately and delete all copies of this message.

Re: Slow queries after Windows startup

2018-01-11 Thread Robert Zenz 
Have you verified that this is isn't caused by cold filesystem caches?


On 11.01.2018 09:19, POUSSEL, Guillaume wrote:
> Hello,
> 
>  
> 
> I’m running PostgreSQL 9.3 on Windows 7 and I’m having a performance
> issue at startup. I have installed PostgreSQL as a service through Windows
> installer.
> 
> The database size is 3 Go, with 120 tables.
> 
>  
> 
> Every time I try to run queries right after Windows startup, it takes a
> huge amount of time.
> 
> If I restart the PostgreSQL Windows service, queries are way faster.
> 
>  
> 
> I have activated debug log and here is what I get before Windows restart:
> 
> duration: 2.000 ms  parse
> 
> duration: 3.000 ms  bind
> 
> duration: 0.000 ms  execute
> 
> And after Windows restart:
> 
> duration: 364.000 ms  parse
> 
> duration: 415.000 ms  bind
> 
> duration: 0.000 ms  execute
> 
> 
> For information, the test query is:
> 
> SELECT t.typlen FROM pg_catalog.pg_type t, pg_catalog.pg_namespace n WHERE
> t.typnamespace=n.oid AND t.typname='name' AND n.nspname='pg_catalog'
> 
> It’s not related to the query itself since other queries give the same
> result (from 10x to 100x longer).
> 
>  
> 
> Here are my settings (all log and locale-related settings omitted on
> purpose):
> 
> 
> bytea_output
> 
> escape
> 
> session
> 
> 
> checkpoint_segments
> 
> 45
> 
> configuration file
> 
> 
> client_encoding
> 
> UNICODE
> 
> session
> 
> 
> client_min_messages
> 
> notice
> 
> session
> 
> 
> DateStyle
> 
> ISO, DMY
> 
> session
> 
> 
> debug_pretty_print
> 
> on
> 
> configuration file
> 
> 
> debug_print_plan
> 
> on
> 
> configuration file
> 
> 
> default_text_search_config
> 
> pg_catalog.french
> 
> configuration file
> 
> 
> listen_addresses
> 
> *
> 
> configuration file
> 
> 
> logging_collector
> 
> on
> 
> configuration file
> 
> 
> max_connections
> 
> 100
> 
> configuration file
> 
> 
> max_stack_depth
> 
> 2MB
> 
> environment variable
> 
> 
> port
> 
> 5432
> 
> configuration file
> 
> 
> shared_buffers
> 
> 128MB
> 
> configuration file
> 
> 
> TimeZone
> 
> GMT
> 
> user
> 
>  
> 
> I run queries through JDBC driver (9.3-1100-jdbc4.jar). I know that the
> issue is not related to the PC, since it give the same result on a bunch of
> different computers.
> 
>  
> 
> I have two questions:
> 
> * What is the difference between restarting PostgreSQL service and
> restarting the computer? Is PostgreSQL relying on some kind of OS-level
> cache outside Windows service?
> 
> * How can I dig down deeper and see what’s causing PostgreSQL
> slowdown?
> 
>  
> 
> Thanks in advance for your help,
> 
> BR,
> 
>  
> 
> Guillaume POUSSEL | ♠Sogeti High Tech
> 
>   [email protected]
> 
>  
> 
>  
> 
>  
> 
>  
> 
>  
> 
> 
> 
> 
> This message contains information that may be privileged or confidential and 
> is the property of the Capgemini Group. It is intended only for the person to 
> whom it is addressed. If you are not the intended recipient, you are not 
> authorized to read, print, retain, copy, disseminate, distribute, or use this 
> message or any part thereof. If you receive this message in error, please 
> notify the sender immediately and delete all copies of this message.
>

RE: Slow queries after Windows startup

2018-01-11 Thread POUSSEL, Guillaume 
No, I have not checked it.
How can I monitor it on Windows? Do you know a tool that can help me?

Thanks!

-Message d'origine-
De : Robert Zenz [mailto:[email protected]] 
Envoyé : jeudi 11 janvier 2018 10:01
À : [email protected]
Objet : Re: Slow queries after Windows startup

Have you verified that this is isn't caused by cold filesystem caches?


On 11.01.2018 09:19, POUSSEL, Guillaume wrote:
> Hello,
> 
>  
> 
> I’m running PostgreSQL 9.3 on Windows 7 and I’m having a performance 
> issue at startup. I have installed PostgreSQL as a service through 
> Windows installer.
> 
> The database size is 3 Go, with 120 tables.
> 
>  
> 
> Every time I try to run queries right after Windows startup, it takes 
> a huge amount of time.
> 
> If I restart the PostgreSQL Windows service, queries are way faster.
> 
>  
> 
> I have activated debug log and here is what I get before Windows restart:
> 
> duration: 2.000 ms  parse
> 
> duration: 3.000 ms  bind
> 
> duration: 0.000 ms  execute
> 
> And after Windows restart:
> 
> duration: 364.000 ms  parse
> 
> duration: 415.000 ms  bind
> 
> duration: 0.000 ms  execute
> 
> 
> For information, the test query is:
> 
> SELECT t.typlen FROM pg_catalog.pg_type t, pg_catalog.pg_namespace n 
> WHERE t.typnamespace=n.oid AND t.typname='name' AND n.nspname='pg_catalog'
> 
> It’s not related to the query itself since other queries give the same 
> result (from 10x to 100x longer).
> 
>  
> 
> Here are my settings (all log and locale-related settings omitted on
> purpose):
> 
> 
> bytea_output
> 
> escape
> 
> session
> 
> 
> checkpoint_segments
> 
> 45
> 
> configuration file
> 
> 
> client_encoding
> 
> UNICODE
> 
> session
> 
> 
> client_min_messages
> 
> notice
> 
> session
> 
> 
> DateStyle
> 
> ISO, DMY
> 
> session
> 
> 
> debug_pretty_print
> 
> on
> 
> configuration file
> 
> 
> debug_print_plan
> 
> on
> 
> configuration file
> 
> 
> default_text_search_config
> 
> pg_catalog.french
> 
> configuration file
> 
> 
> listen_addresses
> 
> *
> 
> configuration file
> 
> 
> logging_collector
> 
> on
> 
> configuration file
> 
> 
> max_connections
> 
> 100
> 
> configuration file
> 
> 
> max_stack_depth
> 
> 2MB
> 
> environment variable
> 
> 
> port
> 
> 5432
> 
> configuration file
> 
> 
> shared_buffers
> 
> 128MB
> 
> configuration file
> 
> 
> TimeZone
> 
> GMT
> 
> user
> 
>  
> 
> I run queries through JDBC driver (9.3-1100-jdbc4.jar). I know that 
> the issue is not related to the PC, since it give the same result on a 
> bunch of different computers.
> 
>  
> 
> I have two questions:
> 
> * What is the difference between restarting PostgreSQL service and
> restarting the computer? Is PostgreSQL relying on some kind of 
> OS-level cache outside Windows service?
> 
> * How can I dig down deeper and see what’s causing PostgreSQL
> slowdown?
> 
>  
> 
> Thanks in advance for your help,
> 
> BR,
> 
>  
> 
> Guillaume POUSSEL | ♠Sogeti High Tech
> 
>   [email protected]
> 
>  
> 
>  
> 
>  
> 
>  
> 
>  
> 
> 
> 
> 
> This message contains information that may be privileged or confidential and 
> is the property of the Capgemini Group. It is intended only for the person to 
> whom it is addressed. If you are not the intended recipient, you are not 
> authorized to read, print, retain, copy, disseminate, distribute, or use this 
> message or any part thereof. If you receive this message in error, please 
> notify the sender immediately and delete all copies of this message.
> 


smime.p7s
Description: S/MIME cryptographic signature
This message contains information that may be privileged or confidential and is 
the property of the Capgemini Group. It is intended only for the person to whom 
it is addressed. If you are not the intended recipient, you are not authorized 
to read, print, retain, copy, disseminate, distribute, or use this message or 
any part thereof. If you receive this message in error, please notify the 
sender immediately and delete all copies of this message.

Re: Slow queries after Windows startup

2018-01-11 Thread Robert Zenz 
I have no idea to be honest, I haven't done any Windows administration in a long
time.

The best I could find is this:

 * https://docs.microsoft.com/en-us/sysinternals/downloads/rammap
 * https://technet.microsoft.com/en-us/library/cc938589.aspx


On 11.01.2018 10:06, POUSSEL, Guillaume wrote:
> No, I have not checked it.
> How can I monitor it on Windows? Do you know a tool that can help me?
> 
> Thanks!
> 
> -Message d'origine-
> De : Robert Zenz [mailto:[email protected]] 
> Envoyé : jeudi 11 janvier 2018 10:01
> À : [email protected]
> Objet : Re: Slow queries after Windows startup
> 
> Have you verified that this is isn't caused by cold filesystem caches?
> 
> 
> On 11.01.2018 09:19, POUSSEL, Guillaume wrote:
>> Hello,
>>
>>  
>>
>> I’m running PostgreSQL 9.3 on Windows 7 and I’m having a performance 
>> issue at startup. I have installed PostgreSQL as a service through 
>> Windows installer.
>>
>> The database size is 3 Go, with 120 tables.
>>
>>  
>>
>> Every time I try to run queries right after Windows startup, it takes 
>> a huge amount of time.
>>
>> If I restart the PostgreSQL Windows service, queries are way faster.
>>
>>  
>>
>> I have activated debug log and here is what I get before Windows restart:
>>
>> duration: 2.000 ms  parse
>>
>> duration: 3.000 ms  bind
>>
>> duration: 0.000 ms  execute
>>
>> And after Windows restart:
>>
>> duration: 364.000 ms  parse
>>
>> duration: 415.000 ms  bind
>>
>> duration: 0.000 ms  execute
>>
>>
>> For information, the test query is:
>>
>> SELECT t.typlen FROM pg_catalog.pg_type t, pg_catalog.pg_namespace n 
>> WHERE t.typnamespace=n.oid AND t.typname='name' AND n.nspname='pg_catalog'
>>
>> It’s not related to the query itself since other queries give the same 
>> result (from 10x to 100x longer).
>>
>>  
>>
>> Here are my settings (all log and locale-related settings omitted on
>> purpose):
>>
>>
>> bytea_output
>>
>> escape
>>
>> session
>>
>>
>> checkpoint_segments
>>
>> 45
>>
>> configuration file
>>
>>
>> client_encoding
>>
>> UNICODE
>>
>> session
>>
>>
>> client_min_messages
>>
>> notice
>>
>> session
>>
>>
>> DateStyle
>>
>> ISO, DMY
>>
>> session
>>
>>
>> debug_pretty_print
>>
>> on
>>
>> configuration file
>>
>>
>> debug_print_plan
>>
>> on
>>
>> configuration file
>>
>>
>> default_text_search_config
>>
>> pg_catalog.french
>>
>> configuration file
>>
>>
>> listen_addresses
>>
>> *
>>
>> configuration file
>>
>>
>> logging_collector
>>
>> on
>>
>> configuration file
>>
>>
>> max_connections
>>
>> 100
>>
>> configuration file
>>
>>
>> max_stack_depth
>>
>> 2MB
>>
>> environment variable
>>
>>
>> port
>>
>> 5432
>>
>> configuration file
>>
>>
>> shared_buffers
>>
>> 128MB
>>
>> configuration file
>>
>>
>> TimeZone
>>
>> GMT
>>
>> user
>>
>>  
>>
>> I run queries through JDBC driver (9.3-1100-jdbc4.jar). I know that 
>> the issue is not related to the PC, since it give the same result on a 
>> bunch of different computers.
>>
>>  
>>
>> I have two questions:
>>
>> * What is the difference between restarting PostgreSQL service and
>> restarting the computer? Is PostgreSQL relying on some kind of 
>> OS-level cache outside Windows service?
>>
>> * How can I dig down deeper and see what’s causing PostgreSQL
>> slowdown?
>>
>>  
>>
>> Thanks in advance for your help,
>>
>> BR,
>>
>>  
>>
>> Guillaume POUSSEL | ♠Sogeti High Tech
>>
>>   [email protected]
>>
>>  
>>
>>  
>>
>>  
>>
>>  
>>
>>  
>>
>>
>>
>>
>> This message contains information that may be privileged or confidential and 
>> is the property of the Capgemini Group. It is intended only for the person 
>> to whom it is addressed. If you are not the intended recipient, you are not 
>> authorized to read, print, retain, copy, disseminate, distribute, or use 
>> this message or any part thereof. If you receive this message in error, 
>> please notify the sender immediately and delete all copies of this message.
>>
>>
>>
>> This message contains information that may be privileged or confidential and 
>> is the property of the Capgemini Group. It is intended only for the person 
>> to whom it is addressed. If you are not the intended recipient, you are not 
>> authorized to read, print, retain, copy, disseminate, distribute, or use 
>> this message or any part thereof. If you receive this message in error, 
>> please notify the sender immediately and delete all copies of this message.

RE: Slow queries after Windows startup

2018-01-11 Thread POUSSEL, Guillaume 
Thanks for pointing out those links. I am trying to figure out how they can 
help me.
One more thing, I can't understand the postgresql.log duration vs. a "EXPLAIN 
ANALYZE" in the query:
Postgresql.log gives:
duration: 628.000 ms  parse (...)
duration: 0.000 ms  bind  (...)
duration: 378.000 ms  execute (...)

EXPLAIN gives:
(...)
I/O Timings: read=0.019
(...)
Total runtime: 0.167 ms

Where are all these milliseconds (378ms vs. 0.167ms)?
What can be slowing down the query parsing?


-Message d'origine-
De : Robert Zenz [mailto:[email protected]] 
Envoyé : jeudi 11 janvier 2018 10:55
À : [email protected]
Objet : Re: Slow queries after Windows startup

I have no idea to be honest, I haven't done any Windows administration in a 
long time.

The best I could find is this:

 * https://docs.microsoft.com/en-us/sysinternals/downloads/rammap
 * https://technet.microsoft.com/en-us/library/cc938589.aspx


On 11.01.2018 10:06, POUSSEL, Guillaume wrote:
> No, I have not checked it.
> How can I monitor it on Windows? Do you know a tool that can help me?
> 
> Thanks!
> 
> -Message d'origine-
> De : Robert Zenz [mailto:[email protected]]
> Envoyé : jeudi 11 janvier 2018 10:01
> À : [email protected]
> Objet : Re: Slow queries after Windows startup
> 
> Have you verified that this is isn't caused by cold filesystem caches?
> 
> 
> On 11.01.2018 09:19, POUSSEL, Guillaume wrote:
>> Hello,
>>
>>  
>>
>> I’m running PostgreSQL 9.3 on Windows 7 and I’m having a performance 
>> issue at startup. I have installed PostgreSQL as a service through 
>> Windows installer.
>>
>> The database size is 3 Go, with 120 tables.
>>
>>  
>>
>> Every time I try to run queries right after Windows startup, it takes 
>> a huge amount of time.
>>
>> If I restart the PostgreSQL Windows service, queries are way faster.
>>
>>  
>>
>> I have activated debug log and here is what I get before Windows restart:
>>
>> duration: 2.000 ms  parse
>>
>> duration: 3.000 ms  bind
>>
>> duration: 0.000 ms  execute
>>
>> And after Windows restart:
>>
>> duration: 364.000 ms  parse
>>
>> duration: 415.000 ms  bind
>>
>> duration: 0.000 ms  execute
>>
>>
>> For information, the test query is:
>>
>> SELECT t.typlen FROM pg_catalog.pg_type t, pg_catalog.pg_namespace n 
>> WHERE t.typnamespace=n.oid AND t.typname='name' AND n.nspname='pg_catalog'
>>
>> It’s not related to the query itself since other queries give the 
>> same result (from 10x to 100x longer).
>>
>>  
>>
>> Here are my settings (all log and locale-related settings omitted on
>> purpose):
>>
>>
>> bytea_output
>>
>> escape
>>
>> session
>>
>>
>> checkpoint_segments
>>
>> 45
>>
>> configuration file
>>
>>
>> client_encoding
>>
>> UNICODE
>>
>> session
>>
>>
>> client_min_messages
>>
>> notice
>>
>> session
>>
>>
>> DateStyle
>>
>> ISO, DMY
>>
>> session
>>
>>
>> debug_pretty_print
>>
>> on
>>
>> configuration file
>>
>>
>> debug_print_plan
>>
>> on
>>
>> configuration file
>>
>>
>> default_text_search_config
>>
>> pg_catalog.french
>>
>> configuration file
>>
>>
>> listen_addresses
>>
>> *
>>
>> configuration file
>>
>>
>> logging_collector
>>
>> on
>>
>> configuration file
>>
>>
>> max_connections
>>
>> 100
>>
>> configuration file
>>
>>
>> max_stack_depth
>>
>> 2MB
>>
>> environment variable
>>
>>
>> port
>>
>> 5432
>>
>> configuration file
>>
>>
>> shared_buffers
>>
>> 128MB
>>
>> configuration file
>>
>>
>> TimeZone
>>
>> GMT
>>
>> user
>>
>>  
>>
>> I run queries through JDBC driver (9.3-1100-jdbc4.jar). I know that 
>> the issue is not related to the PC, since it give the same result on 
>> a bunch of different computers.
>>
>>  
>>
>> I have two questions:
>>
>> * What is the difference between restarting PostgreSQL service and
>> restarting the computer? Is PostgreSQL relying on some kind of 
>> OS-level cache outside Windows service?
>>
>> * How can I dig down deeper and see what’s causing PostgreSQL
>> slowdown?
>>
>>  
>>
>> Thanks in advance for your help,
>>
>> BR,
>>
>>  
>>
>> Guillaume POUSSEL | ♠Sogeti High Tech
>>
>>   [email protected]
>>
>>  
>>
>>  
>>
>>  
>>
>>  
>>
>>  
>>
>>
>>
>>
>> This message contains information that may be privileged or confidential and 
>> is the property of the Capgemini Group. It is intended only for the person 
>> to whom it is addressed. If you are not the intended recipient, you are not 
>> authorized to read, print, retain, copy, disseminate, distribute, or use 
>> this message or any part thereof. If you receive this message in error, 
>> please notify the sender immediately and delete all copies of this message.
>>
>>
>>
>> This message contains information that may be privileged or 
>> confidential and is the property of the Capgemini Group. It is intended only 
>> for the person to whom it is addressed. If you are not the intended 
>> recipient, you are not authorized to read, print, retain, copy, disseminat

Disjunctions and sequential scans

2018-01-11 Thread Ronuk Raval 
Hi there,

This is likely me not understanding something, but I have a query that
I would expect to be fast but PG insists on using a sequential scan.
I've attached a minimized test case but I'll walk through the steps as
well.

I'm running PostgreSQL 10.1 using the standard ArchLinux packages, but
I've been able to reproduce this issue on our production systems
running 9.5 as well.

I have the following 2 tables in a standard users/addresses
configuration with an extra index on addresses to make lookups on the
referring side faster:

CREATE TABLE users (
id integer PRIMARY KEY
);

CREATE TABLE addresses (
id integer PRIMARY KEY,
user_id integer REFERENCES users(id)
);

CREATE INDEX ix_addresses_user_id ON addresses (user_id);

Also, I turn off sequential scanning to force the database to consider
any other plan first:

SET enable_seqscan TO OFF;

Then, I would expect the following query to have a query plan without
any sequential scans:

EXPLAIN (ANALYZE, BUFFERS)
SELECT addresses.id
FROM addresses
WHERE (
addresses.id = 1 OR
EXISTS (
SELECT 1 FROM users
WHERE (
users.id = addresses.user_id AND
users.id = 1
)
)
);

-[ RECORD 1
]
QUERY PLAN | Seq Scan on addresses
(cost=100.00..1018508.10 rows=1130 width=4) (actual
time=0.001..0.001 rows=0 loops=1)
-[ RECORD 2
]
QUERY PLAN |   Filter: ((id = 1) OR (alternatives: SubPlan 1 or
hashed SubPlan 2))
-[ RECORD 3
]
QUERY PLAN |   SubPlan 1
-[ RECORD 4
]
QUERY PLAN | ->  Result  (cost=0.15..8.17 rows=1 width=0)
(never executed)
-[ RECORD 5
]
QUERY PLAN |   One-Time Filter: (addresses.user_id = 1)
-[ RECORD 6
]
QUERY PLAN |   ->  Index Only Scan using users_pkey on
users  (cost=0.15..8.17 rows=1 width=0) (never executed)
-[ RECORD 7
]
QUERY PLAN | Index Cond: (id = 1)
-[ RECORD 8
]
QUERY PLAN | Heap Fetches: 0
-[ RECORD 9
]
QUERY PLAN |   SubPlan 2
-[ RECORD 10
]---
QUERY PLAN | ->  Index Only Scan using users_pkey on users
users_1  (cost=0.15..8.17 rows=1 width=4) (never executed)
-[ RECORD 11
]---
QUERY PLAN |   Index Cond: (id = 1)
-[ RECORD 12
]---
QUERY PLAN |   Heap Fetches: 0
-[ RECORD 13
]---
QUERY PLAN | Planning time: 0.082 ms
-[ RECORD 14
]---
QUERY PLAN | Execution time: 0.032 ms

Given the `Seq Scan on addresses` above, the database clearly
disagrees. What am I missing here?

Strangely, breaking down the query to its components does as I expect.
This is the primary key lookup:

EXPLAIN (ANALYZE, BUFFERS)
SELECT addresses.id
FROM addresses
WHERE addresses.id = 1;

-[ RECORD 1
]-
QUERY PLAN | Index Only Scan using addresses_pkey on addresses
(cost=0.15..8.17 rows=1 width=4) (actual time=0.008..0.008 rows=0
loops=1)
-[ RECORD 2
]-
QUERY PLAN |   Index Cond: (id = 1)
-[ RECORD 3
]--

PGadmin error while connecting with database.

2018-01-11 Thread Dinesh Chandra 12108 
Dear Expert,

While connecting PostgreSQL 9.3 with PGAdmin client I am getting the below 
error.

[cid:[email protected]]

However I am able to connect the database using psql  thourgh Putty.

Entry in pg_hba.conf

# IPv4 local connections:
hostall all 127.0.0.1/32   md5
hostall all 0.0.0.0/0  md5

entry in Postgresql.conf

listen_addresses = '*'
port = 5432

port is already open and I am able to telnet.

Even after creating a new instance and fresh installation of PostgreSQL, I am 
getting the same error.

OS-CentOS 7
S/w-PostgreSQL9.3

Regards,
Dinesh Chandra
|Database administrator (Oracle/PostgreSQL)| Cyient Ltd. Noida.
--
Mobile: +91-9953975849 | Ext 1078 
|[email protected]
Plot No. 7, NSEZ, Phase-II ,Noida-Dadri Road, Noida - 201 305,India.




DISCLAIMER:

This email message is for the sole use of the intended recipient(s) and may 
contain confidential and privileged information. Any unauthorized review, use, 
disclosure or distribution is prohibited. If you are not the intended 
recipient, please contact the sender by reply email and destroy all copies of 
the original message. Check all attachments for viruses before opening them. 
All views or opinions presented in this e-mail are those of the author and may 
not reflect the opinion of Cyient or those of our affiliates.