pgsql: Define a new, more extensible syntax for COPY options.

Started by Tom Lanealmost 17 years ago5 messagescomitters
Jump to latest
#1Tom Lane
tgl@sss.pgh.pa.us

Log Message:
-----------
Define a new, more extensible syntax for COPY options.

This is intentionally similar to the recently revised syntax for EXPLAIN
options, ie, (name value, ...). The old syntax is still supported for
backwards compatibility, but we intend that any options added in future
will be provided only in the new syntax.

Robert Haas, Emmanuel Cecchet

Modified Files:
--------------
pgsql/doc/src/sgml/ref:
copy.sgml (r1.91 -> r1.92)
(http://anoncvs.postgresql.org/cvsweb.cgi/pgsql/doc/src/sgml/ref/copy.sgml?r1=1.91&r2=1.92)
pgsql/src/backend/commands:
copy.c (r1.316 -> r1.317)
(http://anoncvs.postgresql.org/cvsweb.cgi/pgsql/src/backend/commands/copy.c?r1=1.316&r2=1.317)
define.c (r1.105 -> r1.106)
(http://anoncvs.postgresql.org/cvsweb.cgi/pgsql/src/backend/commands/define.c?r1=1.105&r2=1.106)
pgsql/src/backend/parser:
gram.y (r2.677 -> r2.678)
(http://anoncvs.postgresql.org/cvsweb.cgi/pgsql/src/backend/parser/gram.y?r1=2.677&r2=2.678)
pgsql/src/test/regress/expected:
copy2.out (r1.27 -> r1.28)
(http://anoncvs.postgresql.org/cvsweb.cgi/pgsql/src/test/regress/expected/copy2.out?r1=1.27&r2=1.28)
pgsql/src/test/regress/sql:
copy2.sql (r1.18 -> r1.19)
(http://anoncvs.postgresql.org/cvsweb.cgi/pgsql/src/test/regress/sql/copy2.sql?r1=1.18&r2=1.19)

#2Simon Riggs
simon@2ndQuadrant.com
In reply to: Tom Lane (#1)
Re: pgsql: Define a new, more extensible syntax for COPY options.

On Mon, 2009-09-21 at 20:10 +0000, Tom Lane wrote:

Log Message:
-----------
Define a new, more extensible syntax for COPY options.

This is intentionally similar to the recently revised syntax for EXPLAIN
options, ie, (name value, ...). The old syntax is still supported for
backwards compatibility, but we intend that any options added in future
will be provided only in the new syntax.

Can someone add a note to the release checklist to send out infopacks to
specific projects about such changes? It would be useful to let ETL
vendors know we're extending the syntax options so they can support them
by the time we release, rather than 3-6 months after we release.

--
Simon Riggs www.2ndQuadrant.com

#3Bruce Momjian
bruce@momjian.us
In reply to: Simon Riggs (#2)
Re: pgsql: Define a new, more extensible syntax for COPY options.

Simon Riggs wrote:

On Mon, 2009-09-21 at 20:10 +0000, Tom Lane wrote:

Log Message:
-----------
Define a new, more extensible syntax for COPY options.

This is intentionally similar to the recently revised syntax for EXPLAIN
options, ie, (name value, ...). The old syntax is still supported for
backwards compatibility, but we intend that any options added in future
will be provided only in the new syntax.

Can someone add a note to the release checklist to send out infopacks to
specific projects about such changes? It would be useful to let ETL
vendors know we're extending the syntax options so they can support them
by the time we release, rather than 3-6 months after we release.

You mean here?

http://wiki.postgresql.org/wiki/PostgreSQL_8.4_Open_Items

--
Bruce Momjian <bruce@momjian.us> http://momjian.us
EnterpriseDB http://enterprisedb.com

+ If your life is a hard drive, Christ can be your backup. +

#4Simon Riggs
simon@2ndQuadrant.com
In reply to: Bruce Momjian (#3)
Re: pgsql: Define a new, more extensible syntax for COPY options.

On Tue, 2009-09-22 at 14:23 -0400, Bruce Momjian wrote:

Simon Riggs wrote:

On Mon, 2009-09-21 at 20:10 +0000, Tom Lane wrote:

Log Message:
-----------
Define a new, more extensible syntax for COPY options.

This is intentionally similar to the recently revised syntax for EXPLAIN
options, ie, (name value, ...). The old syntax is still supported for
backwards compatibility, but we intend that any options added in future
will be provided only in the new syntax.

Can someone add a note to the release checklist to send out infopacks to
specific projects about such changes? It would be useful to let ETL
vendors know we're extending the syntax options so they can support them
by the time we release, rather than 3-6 months after we release.

You mean here?

http://wiki.postgresql.org/wiki/PostgreSQL_8.4_Open_Items

OK, didn't realise its on the Wiki.

I just added http://wiki.postgresql.org/wiki/PostgreSQL_8.5_Open_Items

--
Simon Riggs www.2ndQuadrant.com

#5Bruce Momjian
bruce@momjian.us
In reply to: Simon Riggs (#4)
Re: pgsql: Define a new, more extensible syntax for COPY options.

Simon Riggs wrote:

On Tue, 2009-09-22 at 14:23 -0400, Bruce Momjian wrote:

Simon Riggs wrote:

On Mon, 2009-09-21 at 20:10 +0000, Tom Lane wrote:

Log Message:
-----------
Define a new, more extensible syntax for COPY options.

This is intentionally similar to the recently revised syntax for EXPLAIN
options, ie, (name value, ...). The old syntax is still supported for
backwards compatibility, but we intend that any options added in future
will be provided only in the new syntax.

Can someone add a note to the release checklist to send out infopacks to
specific projects about such changes? It would be useful to let ETL
vendors know we're extending the syntax options so they can support them
by the time we release, rather than 3-6 months after we release.

You mean here?

http://wiki.postgresql.org/wiki/PostgreSQL_8.4_Open_Items

OK, didn't realise its on the Wiki.

I just added http://wiki.postgresql.org/wiki/PostgreSQL_8.5_Open_Items

Yea, I guess we had not set up a page for 8.5 yet.

--
Bruce Momjian <bruce@momjian.us> http://momjian.us
EnterpriseDB http://enterprisedb.com

+ If your life is a hard drive, Christ can be your backup. +