Re: pgbench - allow backslash continuations in \set expressions
От | Christoph Berg |
---|---|
Тема | Re: pgbench - allow backslash continuations in \set expressions |
Дата | |
Msg-id | 20161003124646.fizunc7gqyfzkriq@msg.df7cb.de обсуждение исходный текст |
Ответ на | Re: pgbench - allow backslash continuations in \set expressions (Fabien COELHO <coelho@cri.ensmp.fr>) |
Ответы |
Re: pgbench - allow backslash continuations in \set expressions
|
Список | pgsql-hackers |
Re: Fabien COELHO 2016-10-03 <alpine.DEB.2.20.1610031259400.19411@lancre> > > I "\set" a bunch of lengthy SQL commands in there, e.g. > > I agree that this looks like a desirable feature, however I would tend to > see that as material for another independent patch. Sure, my question was by no means intending to stop your pgbench patch from going forward by adding extra requirements. > Hmmm. I'm not sure how this is parsed. If this is considered a string '...', > then maybe \set should wait for the end of the string instead of the end of > the line, i.e. no continuation would be needed... > > \set config ' > SELECT name, ... > CASE ... END > FROM pg_settings > WHERE ...;' I guess that would be the sane solution here, yes. Not adding any \ chars at the end of the line would also mean cut-and-paste of the RHS content would work. Thanks for the feedback! Christoph
В списке pgsql-hackers по дате отправления: