pg.ddx.io  pgsql-bugs@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Michael Paquier <michael@paquier.xyz>
To: Daniel Gustafsson <daniel@yesql.se>
Cc: srinivasulu <srinivasulu@accuracy.com.sg>
Cc: pgsql-bugs@lists.postgresql.org
Subject: Re: BUG #16227: Loss database tables automatically in a couple of days
Date: Mon, 27 Jan 2020 12:16:05 +0900
Message-ID: <20200127031605.GC4913@paquier.xyz> (raw)
In-Reply-To: <253FC2BA-4B15-4C90-A2AA-776799E407B8@yesql.se>
References: <16227-e9da632231da5d2a@postgresql.org>
	<20200123114829.GF1895@paquier.xyz>
	<004e01d5d1e6$1dfb2820$59f17860$@com.sg>
	<253FC2BA-4B15-4C90-A2AA-776799E407B8@yesql.se>

On Fri, Jan 24, 2020 at 02:04:57PM +0100, Daniel Gustafsson wrote:
> I don't think this log dump qualifies as providing details, this is a volunteer
> driven effort where people spend their own time.  Have you gone over them to
> see if there is anything you suspect?  Looking at a single one of these, there
> are numerous DROP TABLE statements in it, and we have no way of knowing if
> thats expected or not.

Yeah.  What I can see from those logs is a bunch of logs mentioning
DDL queries doing what you are complaining about.  What you should try
to understand is from where those come from.  This comes with an effort
from your side, where you need to audit your queries, and put in place
drastic connection policies to your database.  One thing that you
should try to do first is enable log_connections and
log_disconnections.  A second is to track down the process which may
be doing that.  And that's not an issue with Postgres, that's an issue
with your server.  Postgres here simply does what it is told to.
--
Michael

Attachments:

  signature.asc (application/pgp-signature, 832B) download

view thread (5+ messages)

Message-ID: <20200127031605.GC4913@paquier.xyz>
Permalink:  ../20200127031605.GC4913@paquier.xyz/
Also on:    postgresql.org/message-id/20200127031605.GC4913@paquier.xyz

 · 

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: michael@paquier.xyz, daniel@yesql.se, srinivasulu@accuracy.com.sg
  Subject: Re: BUG #16227: Loss database tables automatically in a couple of days
  In-Reply-To: <20200127031605.GC4913@paquier.xyz>
  References: <16227-e9da632231da5d2a@postgresql.org> <20200123114829.GF1895@paquier.xyz> <004e01d5d1e6$1dfb2820$59f17860$@com.sg> <253FC2BA-4B15-4C90-A2AA-776799E407B8@yesql.se> <20200127031605.GC4913@paquier.xyz>

* 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