public inbox for [email protected]  

help / color / mirror / Atom feed

From: Adrian Klaver <[email protected]>
To: Peter 'PMc' Much <[email protected]>
Cc: [email protected]
Cc: [email protected]
Subject: Re: failure to drop table due to pg_temp_7 schema
Date: Mon, 17 Nov 2025 14:59:34 -0800
Message-ID: <[email protected]> (raw)
In-Reply-To: <[email protected]>
References: <[email protected]>
	<[email protected]>
	<[email protected]>
	<[email protected]>
	<[email protected]>
	<[email protected]>
	<[email protected]>

On 11/17/25 14:08, Peter 'PMc' Much wrote:
> On Sat, Nov 15, 2025 at 02:10:49PM -0800, Adrian Klaver wrote:

> ! Where is delightfulness short changed in?:
> !
> ! https://www.postgresql.org/docs/18/release-18.html#RELEASE-18-HIGHLIGHTS
> 
> Oh yes, these are fine things, and I know people will be delighted.
> But, honestly, none of them would make me upgrade, as I do not
> currently have a specific usecase.

Alright so what makes you happy. The chance the project make everyone 
happy for any given release is slim to none. That is the consequence of 
developing a general purpose piece of software.


> But these things do happen, the web has a lot of articles on
> switching off nestloop, and you can't store statistics for a CTE
> before invoking the query.

Your problem description is sort of broad, have you tried MATERIALIZED 
or NOT MATERIALIZED as the case may be?

Otherwise start a new thread with a more complete description of the 
issue including EXPLAIN ANALYZE that might help folks troubleshoot the 
problem.


> 
> With Rel.13 came a new fashion of backup, and I was against it.
> I think I mentioned it here, and that was not well received - it's
> necessary for safety, was the bottomline.

What new fashion of backup and what is your issue with it?

Why could you not use an older type of backup?

> 
> So I sat down and wrote the new backup routine, all precisely
> according to the book - since my backup tool didn't have
> anything suitable to offer, at that time.
> Then finally, last year or so, they (Bareos) came along with a proper
> backup routine, and I wanted to switch. But before retiring my own
> script, I wanted to see if the restore would actually work as smooth
> as I had imagined. (I do not normally do restore tests, I think the
> logical proof that the correct data is saved to the correct place,
> should suffice.)

To me, "...correct data is saved to the correct place, ...",  is only 
correct if you can use it to recreate the database instance or the 
entire cluster. In other words prove the restore process works.


> cheers,
> PMc


-- 
Adrian Klaver
[email protected]

view thread (5+ messages)

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: [email protected]
  Cc: [email protected], [email protected], [email protected], [email protected]
  Subject: Re: failure to drop table due to pg_temp_7 schema
  In-Reply-To: <[email protected]>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by agora; see mirroring instructions
for how to clone and mirror all data and code used for this inbox