Re: pgbench - allow backslash continuations in \set expressions - Mailing list pgsql-hackers

From Christoph Berg
Subject Re: pgbench - allow backslash continuations in \set expressions
Date
Msg-id 20161003104344.a6v7z543eaq76yb2@msg.df7cb.de
Whole thread Raw
In response to pgbench - allow backslash continuations in \set expressions  (Fabien COELHO <coelho@cri.ensmp.fr>)
Responses Re: pgbench - allow backslash continuations in \set expressions  (Fabien COELHO <coelho@cri.ensmp.fr>)
List pgsql-hackers
Re: Fabien COELHO 2016-10-03 <alpine.DEB.2.20.1610031049310.19411@lancre>
>
> Attached patch does what is described in the title, hopefully. Continuations
> in other pgbench backslash-commands should be dealt with elsewhere...

Would (a similar version of) that patch also apply to .psqlrc? I
"\set" a bunch of lengthy SQL commands in there, e.g.

\set config 'SELECT name, current_setting(name), CASE source WHEN $$configuration file$$ THEN
sourcefile||$$:$$||sourcelineELSE source END FROM pg_settings WHERE source <> $$default$$;' 

Being able to split that over several lines would greatly improve
maintainability. (Though I do realize this would also require a notion
for splitting/continuing strings.)

Christoph

pgsql-hackers by date:

Previous
From: Heikki Linnakangas
Date:
Subject: Re: Tuplesort merge pre-reading
Next
From: Kyotaro HORIGUCHI
Date:
Subject: Re: asynchronous execution