| From: | "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com> |
|---|---|
| To: | Олег Самойлов <splarv(at)ya(dot)ru> |
| Cc: | Bruce Momjian <bruce(at)momjian(dot)us>, Pg Docs <pgsql-docs(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: Create a Foreign Table for PostgreSQL CSV Logs |
| Date: | 2020-08-24 14:40:49 |
| Message-ID: | CAKFQuwY=pgJLDfcmy6T0_mjL0RGcZQFFALKM=_q9YkfAhmiVcA@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-docs |
On Mon, Aug 24, 2020 at 6:17 AM Олег Самойлов <splarv(at)ya(dot)ru> wrote:
> There must not be constraints at all. Constraints are needed to check
> incoming data to the table. But here table is read-only for database!
>
Please don't top-post.
> So all your constraints is totally useless.
> > > could become:
> > >
> > > connection_from text check(connection_from ~ '^[^:]+:[0-9]+$) -- the
> host and
> > > port of the client, colon-separated
>
I'll agree that the benefit for adding the constraints to a foreign table
are less than for a normal table but it is still not zero. Constraints are
also a form of documentation. And also can be used (at least non-null
ones) during optimization.
David J.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Bruce Momjian | 2020-08-24 15:00:56 | Re: Procedures |
| Previous Message | Bruce Momjian | 2020-08-24 14:22:17 | Re: Document "59.2. Built-in Operator Classes" have a clerical error? |