pg.ddx.io  pgsql-bugs@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: srinivasulu <srinivasulu@accuracy.com.sg>
To: 'Michael Paquier' <michael@paquier.xyz>
To: pgsql-bugs@lists.postgresql.org
Subject: RE: BUG #16227: Loss database tables automatically in a couple of days
Date: Thu, 23 Jan 2020 17:40:31 +0530
Message-ID: <004e01d5d1e6$1dfb2820$59f17860$@com.sg> (raw)
In-Reply-To: <20200123114829.GF1895@paquier.xyz>
References: <16227-e9da632231da5d2a@postgresql.org>
	<20200123114829.GF1895@paquier.xyz>

Please find the attached log file and check it once.

I will send you if you need any details

-----Original Message-----
From: Michael Paquier [mailto:michael@paquier.xyz] 
Sent: Thursday, January 23, 2020 5:18 PM
To: srinivasulu@accuracy.com.sg; pgsql-bugs@lists.postgresql.org
Subject: Re: BUG #16227: Loss database tables automatically in a couple of
days

On Thu, Jan 23, 2020 at 10:03:37AM +0000, PG Bug reporting form wrote:
> Every couple of days we are loosing our postgres server database 
> tables automcaticaly.
> Please check this issue and give us a solution to avoid that..

It is impossible to know what is happening to you if you provide zero
details.  Tables going away would mean that DROP TABLE commands are issues,
so you may want to monitor and audit that.
--
Michael

Attachments:

  postgresql-2020-01-19_000000.log (application/octet-stream, 192.9K) download

  postgresql-2020-01-20_000000.log (application/octet-stream, 200.8K) download

  postgresql-2020-01-21_000000.log (application/octet-stream, 68.8K) download

  postgresql-2020-01-21_204408.log (application/octet-stream, 29.4K) download

  postgresql-2020-01-22_000000.log (application/octet-stream, 196.1K) download

  postgresql-2020-01-23_000000.log (application/octet-stream, 33.7K) download

view thread (5+ messages)  latest in thread

Message-ID: <004e01d5d1e6$1dfb2820$59f17860$@com.sg>
Permalink:  ../004e01d5d1e6$1dfb2820$59f17860$@com.sg/
Also on:    postgresql.org/message-id/004e01d5d1e6$1dfb2820$59f17860$@com.sg

 · 

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients from your mail client; the link fills in
  the headers below: reply via email
  Some clients, webmail especially, drop In-Reply-To and References from
  a link, and the reply then starts a new thread: use the mbox below.

  To: pgsql-bugs@postgresql.org
  Cc: srinivasulu@accuracy.com.sg, michael@paquier.xyz
  Subject: Re: BUG #16227: Loss database tables automatically in a couple of days
  In-Reply-To: <004e01d5d1e6$1dfb2820$59f17860$@com.sg>
  References: <16227-e9da632231da5d2a@postgresql.org> <20200123114829.GF1895@paquier.xyz> <004e01d5d1e6$1dfb2820$59f17860$@com.sg>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox