| From: | Emmanuel Cecchet <manu(at)asterdata(dot)com> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | Emmanuel Cecchet <manu(at)asterdata(dot)com>, Robert Haas <robertmhaas(at)gmail(dot)com>, Emmanuel Cecchet <Emmanuel(dot)Cecchet(at)asterdata(dot)com>, Josh Berkus <josh(at)agliodbs(dot)com>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: generic copy options |
| Date: | 2009-09-17 14:44:28 |
| Message-ID: | 4AB24B4C.8090404@asterdata.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Tom Lane wrote:
> Emmanuel Cecchet <manu(at)asterdata(dot)com> writes:
>
>> Tom Lane wrote:
>>
>>> psql has MORE need to support old syntax than the backend does, because
>>> it's supposed to work against old servers.
>>>
>>>
>> Well, I wonder how many users just upgrade psql vs upgrade the server.
>>
>
> We have established a project policy that psql backslash commands will
> support servers at least back to 7.4, and a great deal of work has
> already been expended in support of that goal. It is not within the
> charter of this patch to ignore or redefine that policy.
>
Does that mean that we can drop the 7.3 syntax or should we just keep it?
For future references, where can I find the various project policies?
Thanks
Emmanuel
--
Emmanuel Cecchet
Aster Data Systems
Web: http://www.asterdata.com
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2009-09-17 14:45:23 | Re: Feedback on getting rid of VACUUM FULL |
| Previous Message | Tom Lane | 2009-09-17 14:32:42 | Re: Feedback on getting rid of VACUUM FULL |