Movatterモバイル変換

[0]ホーム
URL:

Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

 Sign up
Appearance settings

Commit1840d9f

Browse files
committed
doc: Simplify example of HISTFILE for psql
e4c7619 has added a space to the example used for HISTFILE in the docsof psql before the variable DBNAME, as a workaround because variableswere not parsed the same way back then. This behavior has changed in9.2, causing the example in the psql docs to result in the same historyfile created with or without a space added before the DBNAME variable.Let's just remove this space in the example, to reduce any confusion, asthe point of it is to prove that a per-database history file is easy toset up, and that's easier to read this way.Per discussion with Tom Lane.Reported-by: Ludovic KutyDiscussion:https://postgr.es/m/161830067409.691.16198363670687811485@wrigleys.postgresql.org
1 parentcbae877 commit1840d9f

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

‎doc/src/sgml/ref/psql-ref.sgml

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -3915,7 +3915,7 @@ bar
39153915
or <filename>%APPDATA%\postgresql\psql_history</filename> on Windows.
39163916
For example, putting:
39173917
<programlisting>
3918-
\set HISTFILE ~/.psql_history-:DBNAME
3918+
\set HISTFILE ~/.psql_history-:DBNAME
39193919
</programlisting>
39203920
in <filename>~/.psqlrc</filename> will cause
39213921
<application>psql</application> to maintain a separate history for

0 commit comments

Comments
 (0)
[8]ページ先頭
©2009-2025 Movatter.jp