| From: | hubert depesz lubaczewski <depesz(at)depesz(dot)com> |
|---|---|
| To: | Jim Jones <jim(dot)jones(at)uni-muenster(dot)de> |
| Cc: | Matheus Alcantara <matheusssilv97(at)gmail(dot)com>, pgsql-hackers(at)lists(dot)postgresql(dot)org |
| Subject: | Re: Add CREATE SCHEMA ... LIKE support |
| Date: | 2026-02-06 15:35:28 |
| Message-ID: | aYYKQDln_qjA_CdA@depesz.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Fri, Feb 06, 2026 at 04:23:45PM +0100, Jim Jones wrote:
>
>
> On 06/02/2026 15:42, Matheus Alcantara wrote:
> > On 06/02/26 11:35, Jim Jones wrote:
> >> So EXCEPT instead of EXCLUDING and LIMIT TO instead of INCLUDING. Of
> >> course, assuming the proposed syntax isn't already defined in the SQL
> >> standard.
> >>
> >
> > Yeah, it could be an option but IMHO adding the LIKE on CREATE SCHEMA
> > sounds more similar to what we already have for CREATE TABLE ... LIKE.
> >
> > Although I prefer the CREATE SCHEMA LIKE syntax I'm open to discuss
> > about other syntaxes.
>
> Just to be clear, I also like the CREATE SCHEMA <name> LIKE
> <source_schema> syntax. I was just suggesting to consider changing
> EXCLUDING and INCLUDING to EXCEPT and LIMIT TO, respectively. Just to
> make it more consistent with IMPORT FOREIGN SCHEMA, although I find
> INCLUDING and EXCLUDING way more intuitive :)
The way I see it EXCLUDING and INCLUDING are for TYPES of objects (like:
EXCLUDING indexes), while EXCEPT and LIMIT TO are for specific objects
(EXCEPT users).
Best regards,
depesz
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Florents Tselai | 2026-02-06 15:36:34 | doc: add note that wal_level=logical doesn't set up logical replication in itself |
| Previous Message | Andrew Dunstan | 2026-02-06 15:33:55 | Re: [PING] fallocate() causes btrfs to never compress postgresql files |