Re: Need to fix one more glitch in upgrade to -10.2 - Mailing list pgsql-general

From Rich Shepard
Subject Re: Need to fix one more glitch in upgrade to -10.2
Date
Msg-id alpine.LNX.2.20.1802180925480.10894@salmo.appl-ecosys.com
Whole thread Raw
In response to Re: Need to fix one more glitch in upgrade to -10.2  (Adrian Klaver <adrian.klaver@aklaver.com>)
Responses Re: Need to fix one more glitch in upgrade to -10.2 [FIXED]  (Rich Shepard <rshepard@appl-ecosys.com>)
List pgsql-general
On Sun, 18 Feb 2018, Adrian Klaver wrote:

>> Is this appropriate?

> Yes.

Adrian,

   Thanks for confirming

> They could not have been removed as they are in the file. I am guessing
> you are saying they are not in use as far as you know. Just a warning(from
> experience), memory is a tricky thing and removing what is thought to be
> inactive roles is a quick way to find they are not.

   Well, one set of roles is related to my former bookkeeping system and that
database had not been removed. Another set of roles was related to a
replacement bookkeeping system I didn't use and I don't recall seeing that
database when I last ran 'psql -l'.

> So can anyone who knows that postgres role is generally always there. If you 
> want to do this at least restrict the user field.

   As I'm the only one here unless someone is sitting here and logging in
under my username they won't see a thing. And no one's going to sit here an
log in as me other than me. :-) One advantage of working from home.

Regards,

Rich



pgsql-general by date:

Previous
From: Vick Khera
Date:
Subject: Re: shared_buffers 8GB maximum
Next
From: Rich Shepard
Date:
Subject: Re: Need to fix one more glitch in upgrade to -10.2 [FIXED]