El 9/1/19 a las 17:38, Ron escribió:
> On 1/9/19 12:19 PM, Martín Marqués wrote:
>> El 9/1/19 a las 14:58, Steve Clark escribió:
>>> Hi List,
>>>
>>> Is there a sure fire way to tell if postgres server is up an
>>> operational. I was testing to see if the
>>> socket at /tmp/.s.PGSQL.5432 existed -
On 1/9/19 12:19 PM, Martín Marqués wrote:
El 9/1/19 a las 14:58, Steve Clark escribió:
Hi List,
Is there a sure fire way to tell if postgres server is up an operational. I was
testing to see if the
socket at /tmp/.s.PGSQL.5432 existed - but I ran into a recent problem on
CentOS 7.5, postgresq
El 9/1/19 a las 14:58, Steve Clark escribió:
> Hi List,
>
> Is there a sure fire way to tell if postgres server is up an operational. I
> was testing to see if the
> socket at /tmp/.s.PGSQL.5432 existed - but I ran into a recent problem on
> CentOS 7.5, postgresql 9.2.24, where the
> socket was
162 | Office: 734-384-6403 | |
Mobile: 7349151444 | Email: scot.kreienk...@la-z-boy.com
> -Original Message-
> From: Steve Clark [mailto:steve.cl...@netwolves.com]
> Sent: Wednesday, January 9, 2019 12:59 PM
> To: pgsql
> Subject: postgres operational
>
> Hi List,
>
Hi List,
Is there a sure fire way to tell if postgres server is up an operational. I was
testing to see if the
socket at /tmp/.s.PGSQL.5432 existed - but I ran into a recent problem on
CentOS 7.5, postgresql 9.2.24, where the
socket was there but my script couldn't read from my database yet.
Th
