</indexterm>

<para>

The following options only apply to the single-user mode.

The following options only apply to the single-user mode

(see <xref linkend="app-postgres-single-user"

endterm="app-postgres-single-user-title">).

</para>

<variablelist>

<term><option>-E</option></term>

<listitem>

<para>

Echo all commands.

Echo all commands to standard output before executing them.

</para>

</listitem>

</varlistentry>

<term><option>-j</option></term>

<listitem>

<para>

Disables use of newline as a statement delimiter.

Use semicolon followed by two newlines, rather than just newline,

as the command entry terminator.

</para>

</listitem>

</varlistentry>

</para>

</refsect1>

<refsect1>

<title>Usage</title>

<refsect1 id="app-postgres-single-user">

<title id="app-postgres-single-user-title">Single-User Mode</title>

<para>

To start a single-user mode server, use a command like

entry terminator; there is no intelligence about semicolons,

as there is in <application>psql</>. To continue a command

across multiple lines, you must type backslash just before each

newline except the last one.

newline except the last one. The backslash and adjacent newline are

both dropped from the input command. Note that this will happen even

when within a string literal or comment.

</para>

<para>

But if you use the <option>-j</> command line switch, then newline does

not terminate command entry. In this case, the server will read the standard input

until the end-of-file (<acronym>EOF</>) marker, then

process the input as a single command string. Backslash-newline is not

treated specially in this case.

But if you use the <option>-j</> command line switch, a single newline

does not terminate command entry; instead, the sequence

semicolon-newline-newline does. That is, type a semicolon immediately

followed by a completely empty line. Backslash-newline is not

treated specially in this mode. Again, there is no intelligence about

such a sequence appearing within a string literal or comment.

</para>

<para>

In either input mode, if you type a semicolon that is not just before or

part of a command entry terminator, it is considered a command separator.

When you do type a command entry terminator, the multiple statements

you've entered will be executed as a single transaction.

</para>

<para>

To quit the session, type <acronym>EOF</acronym>

(<keycombo action="simul"><keycap>Control</><keycap>D</></>, usually).

If you've

used <option>-j</>, two consecutive <acronym>EOF</>s are needed to exit.

If you've entered any text since the last command entry terminator,

then <acronym>EOF</acronym> will be taken as a command entry terminator,

and another <acronym>EOF</> will be needed to exit.

</para>

<para>

Note that the single-user mode server does not provide sophisticated

line-editing features (no command history, for example).

Single-User mode also does not do any background processing, like

automatic checkpoints.

Single-user mode also does not do any background processing, such as

automatic checkpoints or replication.

</para>

</refsect1>

-- src/backend/snowball/snowball.sql.in$

/*

* text search configuration for _LANGNAME_ language

*

* Copyright (c) 2007-2015, PostgreSQL Global Development Group

*

* src/backend/snowball/snowball.sql.in

*

* _LANGNAME_ and certain other macros are replaced for each language;

* see the Makefile for details.

*

* Note: this file is read in single-user -j mode, which means that the

* command terminator is semicolon-newline-newline; whenever the backend

* sees that, it stops and executes what it's got. If you write a lot of

* statements without empty lines between, they'll all get quoted to you

* in any error message about one of them, so don't do that. Also, you

* cannot write a semicolon immediately followed by an empty line in a

* string literal (including a function body!) or a multiline comment.

*/

-- text search configuration for _LANGNAME_ language

CREATE TEXT SEARCH DICTIONARY _DICTNAME_

(TEMPLATE = snowball, Language = _LANGNAME_ _STOPWORDS_);

-- src/backend/snowball/snowball_func.sql.in$

/*

* Create underlying C functions for Snowball stemmers

*

* Copyright (c) 2007-2015, PostgreSQL Global Development Group

*

* src/backend/snowball/snowball_func.sql.in

*

* This file is combined with multiple instances of snowball.sql.in to

* build snowball_create.sql, which is executed during initdb.

*

* Note: this file is read in single-user -j mode, which means that the

* command terminator is semicolon-newline-newline; whenever the backend

* sees that, it stops and executes what it's got. If you write a lot of

* statements without empty lines between, they'll all get quoted to you

* in any error message about one of them, so don't do that. Also, you

* cannot write a semicolon immediately followed by an empty line in a

* string literal (including a function body!) or a multiline comment.

*/

SET search_path = pg_catalog;

staticconstchar*userDoption=NULL;/* -D switch */

staticboolEchoQuery= false;/* -E switch */

staticintUseNewLine=1;/* Use newlines query delimiters (the default) */

staticintUseNewLine=0;/* Use EOF as query delimiters */

staticboolUseSemiNewlineNewline= false;/* -j switch */

staticboolRecoveryConflictPending= false;

InteractiveBackend(StringInfoinBuf)

{

intc;/* character read from getc() */

boolend= false;/* end-of-input flag */

boolbackslashSeen= false;/* have we seen a \ ? */

resetStringInfo(inBuf);

if (UseNewLine)

while ((c=interactive_getc())!=EOF)

{

while ((c=interactive_getc())!=EOF)

if (c=='\n')

{

if (c=='\n')

if (UseSemiNewlineNewline)

{

if (backslashSeen)

if (inBuf->len>1&&

inBuf->data[inBuf->len-1]=='\n'&&

inBuf->data[inBuf->len-2]==';')

{

break;

}

}

{

if (inBuf->len>0&&

inBuf->data[inBuf->len-1]=='\\')

{

inBuf->data[--inBuf->len]='\0';

continue;

}

{

appendStringInfoChar(inBuf,'\n');

break;

}

}

elseif (c=='\\')

backslashSeen= true;

backslashSeen= false;

appendStringInfoChar(inBuf, (char)c);

}

if (c==EOF)

end= true;

}

{

while ((c=interactive_getc())!=EOF)

appendStringInfoChar(inBuf, (char)c);

if (inBuf->len==0)

end= true;

appendStringInfoChar(inBuf, (char)c);

}

if (end)

if (c==EOF&&inBuf->len==0)

returnEOF;

case'j':

if (secure)

UseNewLine=0;

UseSemiNewlineNewline=true;

break;

case'k':

if (pq_is_reading_msg())

ereport(FATAL,

(errcode(ERRCODE_PROTOCOL_VIOLATION),

errmsg("terminating connection because protocol synchronization was lost")));

errmsg("terminating connection because protocol synchronization was lost")));

RESUME_INTERRUPTS();