| From: | Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(dot)com> |
|---|---|
| To: | Fabien COELHO <coelho(at)cri(dot)ensmp(dot)fr>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | Tatsuo Ishii <ishii(at)sraoss(dot)co(dot)jp>, pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: Removing useless \. at the end of copy in pgbench |
| Date: | 2018-08-29 13:24:38 |
| Message-ID: | e27c7e32-73f8-afb0-9b07-5c7c06e7b48e@2ndquadrant.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 29/07/2018 01:59, Fabien COELHO wrote:
> """
> Pgbench is expected to work with all PostgreSQL supported versions at
> the time it is released. Some options may work only with newer servers. It
> may work with older version down to 8.2.
> """
It is generally expected (nowadays) that client programs work
independent of the server version, unless restrictions are specifically
documented (e.g., pg_dump) or there is some obvious feature dependency
(e.g., unlogged tables). So the above paragraph does not add any useful
information. Also, I don't find any reason why 8.2 is the cutoff, and
saying that it may work down to 8.2 (implying that it may not) is
content-free.
--
Peter Eisentraut http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Peter Eisentraut | 2018-08-29 13:27:00 | Re: Continue work on changes to recovery.conf API |
| Previous Message | Peter Eisentraut | 2018-08-29 13:11:50 | Re: some more error location support |