pg_dump issues

From: Дмитрий Воронин <carriingfate92(at)yandex(dot)ru>
To: PostgreSQL mailing lists <pgsql-hackers(at)postgresql(dot)org>
Subject: pg_dump issues
Date: 2017-06-06 03:37:55
Message-ID: 512811496720275@web12m.yandex.ru
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Hello,<div><br /></div><div>We are working on one project with postgres as engeneer.</div><div><br /></div><div>Bellow is list of inconveniences that we are having with postgresql. We would like to solve them as possible.<span style="background-color:rgb(66,133,244);color:rgb(255,255,255);font-family:Roboto,arial,sans-serif;font-size:20px;white-space:pre-wrap;"></span></div><div><br /></div><div>We can't create any schema dump with another (user defined) name. E.g. we dump schema test and we want to save it's dump with test2 name in any format. Those refers to databases dump.</div><div><br /></div><div>So, no one mechanisms to copy one schema to second one or to make aliases for any database object.</div><div><br /></div><div>How can we solve them?</div><div><br /></div><div>Thank you.</div><div><br /></div>

Attachment Content-Type Size
unknown_filename text/html 822 bytes

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Ashutosh Bapat 2017-06-06 04:13:24 Re: Challenges preventing us moving to 64 bit transaction id (XID)?
Previous Message Michael Paquier 2017-06-06 03:09:28 Re: Server ignores contents of SASLInitialResponse