| From: | Jim Jones <jim(dot)jones(at)uni-muenster(dot)de> |
|---|---|
| To: | Matheus Alcantara <matheusssilv97(at)gmail(dot)com>, Marcos Pegoraro <marcos(at)f10(dot)com(dot)br> |
| Cc: | "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com>, "pgsql-hackers(at)lists(dot)postgresql(dot)org" <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: Add CREATE SCHEMA ... LIKE support |
| Date: | 2026-02-14 19:02:45 |
| Message-ID: | 5d8ce6b1-2726-477c-980e-f2113a3e1b45@uni-muenster.de |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 13/02/2026 22:15, Matheus Alcantara wrote:
> Yeah, I agree. I think that we can be less restrictive. The behavior can
> be to allow reference objects from schemas different than source and in
> case some error happen it stop the process. This behavior should be
> documented.
The more I think about it, the more it seems like the safest approach.
As I mentioned upthread, the user might otherwise end up with pretty
much useless tables and the pleasure of having to drop them manually :)
> In case of e.g table partitions which the parent is in different schema
> the overlap error will happen and the the process will stop. For another
> cases like types in different schema it will work normally.
+1
Best, Jim
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Jeff Davis | 2026-02-14 19:39:53 | Re: Expanding HOT updates for expression and partial indexes |
| Previous Message | KAZAR Ayoub | 2026-02-14 15:02:21 | Re: Speed up COPY TO text/CSV parsing using SIMD |