pg.ddx.io  pgsql-bugs@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Adrian Klaver <adrian.klaver@aklaver.com>
To: Ram Pratap Maurya <ram.maurya@lavainternational.in>
To: pgsql-general@lists.postgresql.org <pgsql-general@lists.postgresql.org>
Subject: Re: BUG #17046: Upgrade postgres 11 to 13 version
Date: Thu, 3 Jun 2021 14:37:16 -0700
Message-ID: <0ff2f400-b8ac-c2cd-68a5-702a096c019d@aklaver.com> (raw)
In-Reply-To: <KL1PR0601MB4433B753276F4E27A3587E43F03C9@KL1PR0601MB4433.apcprd06.prod.outlook.com>
References: <17046-653f73611eea8857@postgresql.org>
	<CAApHDvrXp0RrmnofqOpBSMKmzveLwaZZdDFYRDQndCFuH9B45w@mail.gmail.com>
	<KL1PR0601MB4433B753276F4E27A3587E43F03C9@KL1PR0601MB4433.apcprd06.prod.outlook.com>

On 6/3/21 5:53 AM, Ram Pratap Maurya wrote:
> Hi Team,
> 
> I am creating new server and installed postgres -13 and take PG_BACKUP  form current PRD server (PG version 11) and restore DB on PG-13 server.
> can you suggest if we doing upgrade by this activity there is any issue.

When doing this you should use the later version(13) of pg_dump to dump 
the earlier version, are you doing that? If you are then you have 
eliminated one possible issue.

You should also read the Release Notes section of version 12 and 13:

https://www.postgresql.org/docs/12/release.html
https://www.postgresql.org/docs/13/release.html

to see what things have changed that may affect your current set up.
> 
> 
> 
> Regards,
> Ram Pratap.
> 
> -----Original Message-----
> From: David Rowley [mailto:dgrowleyml@gmail.com]
> Sent: 03 June 2021 18:01
> To: Ram Pratap Maurya; PostgreSQL mailing lists
> Subject: Re: BUG #17046: Upgrade postgres 11 to 13 version
> 
> On Fri, 4 Jun 2021 at 00:22, PG Bug reporting form <noreply@postgresql.org> wrote:
>> i am creating new server and installed postgres -13 and take PG_BACKUP
>> form current PRD server (PG version 11) and restore DB on PG-13
>> server. can you suggest if we doing upgrade by this activity there is any issue.
> 
> The form you've used is for reporting bugs yet, this does not seem to be a bug report.
> 
> If you're looking for general help and advice then you should consider asking on one of the mailing lists.
> 
> https://www.postgresql.org/list/
> 
> pgsql-general might be the best fit.
> 
> David
> 


-- 
Adrian Klaver
adrian.klaver@aklaver.com





view thread (6+ messages)  latest in thread

Message-ID: <0ff2f400-b8ac-c2cd-68a5-702a096c019d@aklaver.com>
Permalink:  ../0ff2f400-b8ac-c2cd-68a5-702a096c019d@aklaver.com/
Also on:    postgresql.org/message-id/0ff2f400-b8ac-c2cd-68a5-702a096c019d@aklaver.com

 · 

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-bugs@postgresql.org
  Cc: adrian.klaver@aklaver.com, ram.maurya@lavainternational.in, pgsql-general@lists.postgresql.org
  Subject: Re: BUG #17046: Upgrade postgres 11 to 13 version
  In-Reply-To: <0ff2f400-b8ac-c2cd-68a5-702a096c019d@aklaver.com>

* 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