Horton

Re: Reports on obsolete Postgres versions

Bruce Momjian <bruce@momjian.us>

View thread
From: Bruce Momjian <bruce@momjian.us>
To: Greg Sabino Mullane <htamfids@gmail.com>
Cc: "David G. Johnston" <david.g.johnston@gmail.com>, Magnus Hagander <magnus@hagander.net>, Daniel Gustafsson <daniel@yesql.se>, Robert Treat <rob@xzilla.net>, Jeremy Schneider <schneider@ardentperf.com>, Michael Banck <mbanck@gmx.net>, Nathan Bossart <nathandbossart@gmail.com>, PostgreSQL Hackers <pgsql-hackers@postgresql.org>
Date: 2024-04-12T21:12:06Z
Lists: pgsql-hackers 
On Thu, Apr  4, 2024 at 04:51:50PM -0400, Bruce Momjian wrote:
> On Thu, Apr  4, 2024 at 04:38:10PM -0400, Greg Sabino Mullane wrote:
> > On Thu, Apr 4, 2024 at 2:23 PM Bruce Momjian <bruce@momjian.us> wrote:
> >     +Such upgrades might require manual changes to complete so always read
> >     +the release notes first.
> > 
> > Proposal:
> > "Such upgrades might require additional steps, so always read the release notes
> > first."
> 
> Yes, I modified that sentence.
> 
> >     I went with frequently-encountered and low risk bugs".
> > 
> > But neither of those classifications are really true. Especially the "low risk"
> > part - I could see various ways a reader could wrongly interpret that.
> 
> I see your point.  Updated patch attached.

I am ready to apply this patch to the website.  How do I do this?  Do I
just commit this to the pgweb git tree?  Does that push to the website?

-- 
  Bruce Momjian  <bruce@momjian.us>        https://momjian.us
  EDB                                      https://enterprisedb.com

  Only you can decide what is important to you.