Re: Alternative to \copy in psql modelled after \g

From: Fabien COELHO <coelho(at)cri(dot)ensmp(dot)fr>
To: Daniel Verite <daniel(at)manitou-mail(dot)org>
Cc: PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>, "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com>
Subject: Re: Alternative to \copy in psql modelled after \g
Date: 2018-12-27 16:57:33
Message-ID: alpine.DEB.2.21.1812271737590.32444@lancre
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers


> It looks a significant step forward, to be brought by a patch on its own
> without prospect of being back-patched.

Dunno. Even if an additional tap test would not be backpatched, it could
be added on master. I'm basically sadden by pg test coverage, especially
psql which is under 40%, so I try to grasp any improvement opportunity…

See https://coverage.postgresql.org/

--
Fabien.

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Andrew Dunstan 2018-12-27 16:58:30 Re: GIN predicate locking slows down valgrind isolationtests tremendously
Previous Message Magnus Hagander 2018-12-27 16:53:51 Re: Remove Deprecated Exclusive Backup Mode