Re: [PATCH] Add pg_get_tablespace_ddl() function to reconstruct CREATE TABLESPACE statement - Mailing list pgsql-hackers

From Manni Wood
Subject Re: [PATCH] Add pg_get_tablespace_ddl() function to reconstruct CREATE TABLESPACE statement
Date
Msg-id CAKWEB6pAPjbY7bp7v7b0xq6fGR_ze9f4EsveC5UcaFEzVMMPCw@mail.gmail.com
Whole thread Raw
In response to [PATCH] Add pg_get_tablespace_ddl() function to reconstruct CREATE TABLESPACE statement  (Manni Wood <manni.wood@enterprisedb.com>)
List pgsql-hackers

Manni Wood manni.wood@enterprisedb.com

Attachments8:09 AM (13 minutes ago)
to Álvaropsql-hackersChaoNishantJim
Hello! After waiting all weekend, my Friday e-mail did not get through psql-hackers, so I am sending again, using Álvaro's advice to send to lists.postgresql.org rather than plain postgresql.org.

Here is the original mail:

Hello, Chao Li!

Thank you for the improvements to my patch, helping it follow more of Postgres's coding conventions. Much appreciated.

I have attached v13 of the patch. Now that Álvaro has merged the contents of the 0001 patch, I assume this v13 patch can be 0001 and not 0002.

On Thu, Nov 13, 2025 at 1:59 PM Manni Wood <manni.wood@enterprisedb.com> wrote:


On Thu, Nov 13, 2025 at 12:20 PM Álvaro Herrera <alvherre@kurilemu.de> wrote:
On 2025-Nov-13, Manni Wood wrote:

> Hello, Chao Li!
>
> Thank you for the improvements to my patch, helping it follow more of
> Postgres's coding conventions. Much appreciated.
>
> I have tried attaching a v13 patch and Mailer-Daemon@postgresql.org is
> saying my message is undeliverable to pgsql-hackers@postgresql.org, so I'm
> just sending this message without the attachment to see if it gets through
> and to thank you for looking at the patch.

The problem is just that lists under @postgresql.org are temporarily
broken.  They should be fixed later today.  I suggest you do nothing for
now; your message might be delivered later if it's still in the server
queue (though maybe not -- not sure).

The same addresses but under @lists.postgresql.org would work just fine.
I suggest you use that in new threads (or even in existing threads, going
forward, by manually editing the CC line).  But as I said, for the
current thread I suggest not to resend your message to avoid potential
duplicated messages.

--
Álvaro Herrera        Breisgau, Deutschland  —  https://www.EnterpriseDB.com/
"We're here to devour each other alive"            (Hobbes)

OK, thanks, Álvaro; I will hold off with e-mails until later to see if my already-sent ones eventually get through.
--
-- Manni Wood EDB: https://www.enterprisedb.com


--
-- Manni Wood EDB: https://www.enterprisedb.com
Attachment

pgsql-hackers by date:

Previous
From: tushar
Date:
Subject: Re: Non-text mode for pg_dumpall
Next
From: Daniel Gustafsson
Date:
Subject: Re: [PATCH] Add hints for invalid binary encoding names in encode/decode functions