Re: md5 issues Postgres14 on OL7

On Sat, Jan 08, 2022 at 02:00:16PM -0500, Tom Lane wrote: > This is looking pretty solid to me. Just a couple of nitpicks: > > * In most places you initialize variables holding error strings to NULL: > > + const char *logdetail = NULL; > > but there are three or so spots that don't, eg Perf

Re: DROP OWNED BY fails with #53200: ERROR: out of shared memory

On 1/10/22 13:58, Dominique Devienne wrote: Given that Tom mentions max_locks_per_transaction can be safely increased, and given the stats I mentioned in this thread, what would a "reasonable" max_locks_per_transaction be in my case? By reasonable, I mean "as large as possible w/o being too l

Re: DROP OWNED BY fails with #53200: ERROR: out of shared memory

On Mon, Jan 10, 2022 at 10:29 PM Tom Lane wrote: > "David G. Johnston" writes: > > On Mon, Jan 10, 2022 at 12:09 PM Dominique Devienne > > > wrote: > >> Tom wrote "relation" for the number of locks necessary for DROP OWNED > BY. > >> What does it mean in this context? relation = table? > > > I'

Re: DROP OWNED BY fails with #53200: ERROR: out of shared memory

"David G. Johnston" writes: > On Mon, Jan 10, 2022 at 12:09 PM Dominique Devienne > wrote: >> Tom wrote "relation" for the number of locks necessary for DROP OWNED BY. >> What does it mean in this context? relation = table? > I'm confused here a bit as well. The items being talked about are tab

Re: DROP OWNED BY fails with #53200: ERROR: out of shared memory

On 1/10/22 13:08, David G. Johnston wrote: On Mon, Jan 10, 2022 at 12:09 PM Dominique Devienne > wrote: Given |max_locks_per_transaction| * (max_connections  + ma

Re: DROP OWNED BY fails with #53200: ERROR: out of shared memory

On Mon, Jan 10, 2022 at 12:09 PM Dominique Devienne wrote: > Given max_locks_per_transaction * (max_connections > > + max_prepared_transactions >

Re: DROP OWNED BY fails with #53200: ERROR: out of shared memory

On 2022-Jan-10, Dominique Devienne wrote: > Given max_locks_per_transaction * (max_connections > > + max_prepared_transactions >

Re: DROP OWNED BY fails with #53200: ERROR: out of shared memory

On 1/10/22 11:12, Dominique Devienne wrote: I accidentally replied to Tom only. Here's my response again. Apparently, I'm using the default max_locks_per_transaction: ``` ddevienne=> show max_locks_per_transaction ;  max_locks_per_transaction ---  64 (1 row) ``` To

Re: DROP OWNED BY fails with #53200: ERROR: out of shared memory

I accidentally replied to Tom only. Here's my response again. Apparently, I'm using the default max_locks_per_transaction: ``` ddevienne=> show max_locks_per_transaction ; max_locks_per_transaction --- 64 (1 row) ``` Given max_locks_per_transaction * (max_connections

Re: DROP OWNED BY fails with #53200: ERROR: out of shared memory

Dominique Devienne writes: > I'm trying to DROP a ROLE that has 4 schemas: > * 2 smallish ones (1 or 2 dozen tables each), > * 2 largish ones (250 tables, totalling around 4000 columns each). > And of course there are various indexes, constraints, etc... on each schema. You're going to need a lo

DROP OWNED BY fails with #53200: ERROR: out of shared memory

I'm trying to DROP a ROLE that has 4 schemas: * 2 smallish ones (1 or 2 dozen tables each), * 2 largish ones (250 tables, totalling around 4000 columns each). And of course there are various indexes, constraints, etc... on each schema. This fails with: DDL Error: DROP OWNED BY "Epos-PNS (a73e1fb

Re: Install pg_dump and pg_restore on UBI8 and UBI8-minimal

Hi, On Mon, 2022-01-10 at 09:02 +0100, Torello Querci wrote: > > I'm trying to install pg_dump and pg_restore for Postgres12 on a > docker image based on UBI8 and UBI8-minimal but I don't find any > resources to do that. > There are some packages available or have I to built it from myself? I o

Re: Database stuck in a state where vacuum and vacuumdb is not working

On Mon, 2022-01-10 at 13:19 +, jonathaan67 wrote: > My database server stuck in a state where vacuum and vacuumdb is not working. > Yesterday saw this error: > > > HINT: To avoid a database shutdown, execute a full-database VACUUM in > > "production_services" > > WARNING: database "productio

Database stuck in a state where vacuum and vacuumdb is not working

Hello. My database server stuck in a state where vacuum and vacuumdb is not working. Yesterday saw this error: > HINT: To avoid a database shutdown, execute a full-database VACUUM in > "production_services" > WARNING: database "production_services" must be vacuumed within 10059807 > transaction

CI/CD Boilerplate for extension binaries without source code ?

Hi, For a gig, I’m developing a small Postgres extension, adding a few data types and some functions (some of them written in C and some of them written in plpython3). Now, my client doesn’t want the source code to be visible and/or open even internally to other teams; They just want a bunch

Install pg_dump and pg_restore on UBI8 and UBI8-minimal

Hello, I'm trying to install pg_dump and pg_restore for Postgres12 on a docker image based on UBI8 and UBI8-minimal but I don't find any resources to do that. There are some packages available or have I to built it from myself? Thanks