Re: [HACKERS] psql and comments
От | Peter Eisentraut |
---|---|
Тема | Re: [HACKERS] psql and comments |
Дата | |
Msg-id | Pine.LNX.4.10.9910072348440.848-100000@peter-e.yi.org обсуждение исходный текст |
Ответ на | Re: [HACKERS] psql and comments (Tom Lane <tgl@sss.pgh.pa.us>) |
Список | pgsql-hackers |
On Oct 7, Tom Lane mentioned: > There was talk earlier of changing the behavior so that psql would > forward comments to the backend, rather than stripping them. One > potential annoyance if we do that is that (I think) all the regress > test expected outputs will change because comments will then appear > in them. That is a somewhat separate issue, but good that you bring it up. In my cleaning ways I noticed that the -e vs. -E switches weren't applied correctly so I set that straight to an extent. The regression tests rely on -e to echo the query back correctly, not the one actually sent to the backend, so that could be tweaked. Luckily, the regression tests don't make extensive use of the backslash commands, the issue being that their output might change. I only found three backslash commands in the whole regression tests. One occurence does something like this: some query; *** comment *** comment \p \r more queries; which should probably be changed anyway to something like -- comment -- comment The other case is CREATE TEMP TABLE temptest(col int); -- test temp table deletion \c regression SELECT * FROM temptest; which still works as I just confirmed, and the output of \c gets eaten in -q mode anyway. Seems it's still safe. -- Peter Eisentraut Sernanders vaeg 10:115 peter_e@gmx.net 75262 Uppsala http://yi.org/peter-e/ Sweden
В списке pgsql-hackers по дате отправления: