pg.ddx.io  pgsql-admin@postgresql.org mailing list archive  

help / color / mirror / Atom feed

From: Laurenz Albe <laurenz.albe@cybertec.at>
To: soumik.bhattacharjee@kpn.com
To: tgl@sss.pgh.pa.us
Cc: pgsql-admin@lists.postgresql.org
Subject: Re: Table Drop Error
Date: Mon, 18 Feb 2019 18:56:45 +0100
Message-ID: <cd290b96a427fdc425b8c55f8aa2c27bbce57dad.camel@cybertec.at> (raw)
In-Reply-To: <2A91BEF8171A5349931391E0C721CC531D6DBD3F@CPEMS-KPN301.KPNCNL.LOCAL>
References: <2A91BEF8171A5349931391E0C721CC531D6DB881@CPEMS-KPN301.KPNCNL.LOCAL>
	<3681.1550246571@sss.pgh.pa.us>
	<2A91BEF8171A5349931391E0C721CC531D6DB96D@CPEMS-KPN301.KPNCNL.LOCAL>
	<10223d001b83afa185f5ec689b0cc6591c3fa15f.camel@cybertec.at>
	<2A91BEF8171A5349931391E0C721CC531D6DBD3F@CPEMS-KPN301.KPNCNL.LOCAL>

soumik.bhattacharjee@kpn.com wrote:
> But what is the solution in this case?

Before we can come up with a solution, we have to understand the problem.

Yours,
Laurenz Albe
-- 
Cybertec | https://www.cybertec-postgresql.com

view thread (10+ messages)

Message-ID: <cd290b96a427fdc425b8c55f8aa2c27bbce57dad.camel@cybertec.at>
Permalink:  ../cd290b96a427fdc425b8c55f8aa2c27bbce57dad.camel@cybertec.at/
Also on:    postgresql.org/message-id/cd290b96a427fdc425b8c55f8aa2c27bbce57dad.camel@cybertec.at

copy link · copy postgr.es

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 using the --to and --cc options:
  reply via email

  To: pgsql-admin@postgresql.org
  Cc: laurenz.albe@cybertec.at, soumik.bhattacharjee@kpn.com, tgl@sss.pgh.pa.us, pgsql-admin@lists.postgresql.org
  Subject: Re: Table Drop Error
  In-Reply-To: <cd290b96a427fdc425b8c55f8aa2c27bbce57dad.camel@cybertec.at>

* 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