Re: Create a Foreign Table for PostgreSQL CSV Logs

On Sat, Aug 22, 2020 at 01:51:56PM -0400, Bruce Momjian wrote: > On Fri, Aug 21, 2020 at 08:41:54PM -0700, David G. Johnston wrote: > > On Fri, Aug 21, 2020 at 2:58 PM Bruce Momjian wrote: > > Good idea.  People have been confused about this before.  Attached is a > > patch. > > > > > >

Re: Create a Foreign Table for PostgreSQL CSV Logs

> 26 Aug 2020, в 09:24, Николай Чадаев написал(а): > > Thank You Oleg. > > A simple example is extremely important and necessary. > I will wait for this example. It's already exists. The idea was to add cross links to this.

Re: Create a Foreign Table for PostgreSQL CSV Logs

Thank You Oleg. A simple example is extremely important and necessary.I will wait for this example. -- Nick Chadaev   +7(916)175-3061  +7(958)820-797524.08.2020, 18:38, "Олег Самойлов" :  24 авг. 2020 г., в 18:07, Bruce Momjian написал(а):  On Mon, Aug 2

Re: Create a Foreign Table for PostgreSQL CSV Logs

> 24 авг. 2020 г., в 18:07, Bruce Momjian написал(а): > > On Mon, Aug 24, 2020 at 07:40:49AM -0700, David G. Johnston wrote: >> On Mon, Aug 24, 2020 at 6:17 AM Олег Самойлов wrote: >> >>There must not be constraints at all. Constraints are needed to check >>incoming data to the table

Re: Create a Foreign Table for PostgreSQL CSV Logs

On Mon, Aug 24, 2020 at 07:40:49AM -0700, David G. Johnston wrote: > On Mon, Aug 24, 2020 at 6:17 AM Олег Самойлов 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

Re: Create a Foreign Table for PostgreSQL CSV Logs

On Mon, Aug 24, 2020 at 6:17 AM Олег Самойлов 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: > > >

Re: Create a Foreign Table for PostgreSQL CSV Logs

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! So all your constraints is totally useless. > > could become: > > > > connection_from text check(connection_from ~ '^[^:]+:[0-9]+$) -- the host > > and > >

Re: Create a Foreign Table for PostgreSQL CSV Logs

On Sat, Aug 22, 2020 at 10:51 AM Bruce Momjian wrote: > On Fri, Aug 21, 2020 at 08:41:54PM -0700, David G. Johnston wrote: > > Adding CHECK constraints and -- > > comments to the CREATE TABLE command would be a welcome addition. In > > particular I noticed: > > > > paragraph: client host:port nu

Re: Create a Foreign Table for PostgreSQL CSV Logs

On Fri, Aug 21, 2020 at 08:41:54PM -0700, David G. Johnston wrote: > On Fri, Aug 21, 2020 at 2:58 PM Bruce Momjian wrote: > Good idea.  People have been confused about this before.  Attached is a > patch. > > > + It is also possible to access the file as a foreign data wrapper > +      

Re: Create a Foreign Table for PostgreSQL CSV Logs

On Fri, Aug 21, 2020 at 2:58 PM Bruce Momjian wrote: > On Fri, Aug 21, 2020 at 09:25:20AM +, PG Doc comments form wrote: > > The following documentation comment has been logged on the website: > > > > Page: https://www.postgresql.org/docs/12/runtime-config-logging.html > > Description: > > >

Re: Create a Foreign Table for PostgreSQL CSV Logs

On Fri, Aug 21, 2020 at 09:25:20AM +, PG Doc comments form wrote: > The following documentation comment has been logged on the website: > > Page: https://www.postgresql.org/docs/12/runtime-config-logging.html > Description: > > There is some imperfection in PostgreSQL doc. There are two sect