Andrei updated the doc on aggregates, please see attached (thanks,
Andrei!).
I forgot to mention when I committed his aggregate patch is that
arrary() is not yet supported, but the other aggregate functions are
(see doc for a full list).
Andrei also helpfully sent along COPY syntax:
COPY tablename [ ( column [, ...] ) ]
FROM { 'filename' | STDIN }
[ [ WITH ]
[ OIDS ]
[ DELIMITER [ AS ] 'delimiter' ]
[ NULL [ AS ] 'null string' ]
[ CSV [ HEADER ]
[ QUOTE [ AS ] 'quote' ]
[ ESCAPE [ AS ] 'escape' ]
[ FORCE NOT NULL column [, ...] ]
COPY tablename [ ( column [, ...] ) ]
TO { 'filename' | STDOUT }
[ [ WITH ]
[ OIDS ]
[ DELIMITER [ AS ] 'delimiter' ]
[ NULL [ AS ] 'null string' ]
[ CSV [ HEADER ]
[ QUOTE [ AS ] 'quote' ]
[ ESCAPE [ AS ] 'escape' ]
[ FORCE QUOTE column [, ...] ]
Comparing to Postgres, PGXC does not support BINARY.
Regards,
Mason
Koichi Suzuki wrote:
> Hi,
>
> I'm beginning to write a reference manual for the new feature. I
> need the following info for this.
>
> 1. COPY TO/ COPY FROM statement definition,
> 2. pg_aggregate extension (columns, types and descriptions)
> 3. Any other changes to the catalog.
> 4. Supported aggregate function list.
>
> User function release is scheduled at the end of June so it will not
> be included yet.
>
> For the information of catalog, you may send me .h files.
>
> Also, I think we can add "aggregate function" algorithm to the
> release. Would like to have a comment on this.
>
> Regards;
> ----------
> Koichi Suzuki
>
> ------------------------------------------------------------------------------
>
> _______________________________________________
> Postgres-xc-developers mailing list
> Pos...@li...
> https://lists.sourceforge.net/lists/listinfo/postgres-xc-developers
>
--
Mason Sharp
EnterpriseDB Corporation
The Enterprise Postgres Company
This e-mail message (and any attachment) is intended for the use of
the individual or entity to whom it is addressed. This message
contains information from EnterpriseDB Corporation that may be
privileged, confidential, or exempt from disclosure under applicable
law. If you are not the intended recipient or authorized to receive
this for the intended recipient, any use, dissemination, distribution,
retention, archiving, or copying of this communication is strictly
prohibited. If you have received this e-mail in error, please notify
the sender immediately by reply e-mail and delete this message.
|
