<entry><type>bool</type></entry>

<entry>

Role can log in. That is, this role can be given as the initial

</entry>

</row>

</term>

<listitem>

<para>

</para>

<para>

This parameter is only available if the <symbol>LOCK_DEBUG</symbol>

OK

(1 row)

a | b | c

----+---+---------------

0 | a | {a0,b0,c0}

<para>

The SQL command that you wish to execute in the remote database,

for example

</para>

</listitem>

</varlistentry>

OK

(1 row)

dblink_exec

-----------------

INSERT 943366 1

OK

(1 row)

dblink_exec

------------------

INSERT 6432584 1

obj.object_name,

obj.object_identity;

END LOOP;

$$;

CREATE EVENT TRIGGER test_event_trigger_for_drops

ON sql_drop

if a foreground cleanup does occur, it will take even longer.

</para>

<para>

GIN index to have its own cleanup threshold.

For example, it's possible to increase the threshold only for the GIN

index which can be updated heavily, and decrease it otherwise.

Note that in this mode, the server will apply WAL one file at a

time, so if you use the standby server for queries (see Hot Standby),

there is a delay between an action in the master and when the

to fill up the WAL file. <varname>archive_timeout</> can be used to make that delay

shorter. Also note that you can't combine streaming replication with

this method.

hard-coded list of prefixes; this list of prefixes is also used to hyphenate

numbers on output. Since new prefixes are assigned from time to time, the

list of prefixes may be out of date. It is hoped that a future version of

can be easily updated by users as needed; however, at present, the

list can only be updated by modifying the source code and recompiling.

Alternatively, prefix validation and hyphenation support may be

<para>

The <literal>FOR UPDATE</> lock mode

is also acquired by any <command>DELETE</> on a row, and also by an

the set of columns considered for the <command>UPDATE</> case are those that

have a unique index on them that can be used in a foreign key (so partial

indexes and expressional indexes are not considered), but this may change

</para>

<para>

</para>

<itemizedlist>

SELECT users.userid INTO STRICT userid

FROM users WHERE users.username = get_userid.username;

RETURN userid;

$$ LANGUAGE plpgsql;

</programlisting>

On failure, this function might produce an error message such as

RETURN NEXT r; -- return current row of SELECT

END LOOP;

RETURN;

$BODY$

LANGUAGE plpgsql;

END IF;

RETURN;

$BODY$

LANGUAGE plpgsql;

f1 int;

BEGIN

RETURN f1;

$$ LANGUAGE plpgsql;

WARNING: variable "f1" shadows a previously defined variable

LINE 3: f1 int;

<para>

Every sent transaction contains zero or more DML messages (Insert,

Update, Delete). In case of a cascaded setup it can also contain Origin

different replication node. Since a replication node in the scope of logical

replication protocol can be pretty much anything, the only identifier

is the origin name. It's downstream's responsibility to handle this as

[ FROM <replaceable class="parameter">from_item</replaceable> [, ...] ]

[ WHERE <replaceable class="parameter">condition</replaceable> ]

[ GROUP BY <replaceable class="parameter">grouping_element</replaceable> [, ...] ]

[ WINDOW <replaceable class="parameter">window_name</replaceable> AS ( <replaceable class="parameter">window_definition</replaceable> ) [, ...] ]

[ { UNION | INTERSECT | EXCEPT } [ ALL | DISTINCT ] <replaceable class="parameter">select</replaceable> ]

[ ORDER BY <replaceable class="parameter">expression</replaceable> [ ASC | DESC | USING <replaceable class="parameter">operator</replaceable> ] [ NULLS { FIRST | LAST } ] [, ...] ]

[ FROM <replaceable class="parameter">from_item</replaceable> [, ...] ]

[ WHERE <replaceable class="parameter">condition</replaceable> ]

[ GROUP BY <replaceable class="parameter">expression</replaceable> [, ...] ]

[ WINDOW <replaceable class="parameter">window_name</replaceable> AS ( <replaceable class="parameter">window_definition</replaceable> ) [, ...] ]

[ { UNION | INTERSECT | EXCEPT } [ ALL | DISTINCT ] <replaceable class="parameter">select</replaceable> ]

[ ORDER BY <replaceable class="parameter">expression</replaceable> [ ASC | DESC | USING <replaceable class="parameter">operator</replaceable> ] [ NULLS { FIRST | LAST } ] [, ...] ]

</para>

<para>

that the planner has all

the information about which tables have to be scanned plus the

relationships between these tables plus the restrictive

the best path to execute the query, and the more information

the planner has, the better this decision can be. And

the rule system as implemented in <productname>PostgreSQL</productname>

up to that point.

</para>

</sect2>

BEGIN

RAISE NOTICE '% =&gt; %', $1, $2;

RETURN true;

$$ LANGUAGE plpgsql COST 0.0000000000000000000001;

SELECT * FROM phone_number WHERE tricky(person, phone);

</table>

<para>

creates a parsing ambiguity: it is not clear whether the upper bound

in <literal>0...23</> is meant to be <literal>23</> or <literal>0.23</>.

This is resolved by requiring at least one digit before the decimal

positions in <type>tsvector</type>, which in turn affect ranking:

<screen>

to_tsvector

----------------------------

'list':3 'stop':5 'word':6

calculated for documents with and without stop words are quite different:

<screen>

ts_rank_cd

------------

0.05

ts_rank_cd

------------

0.1

Now we can test our dictionary:

<screen>

ts_lexize

-----------

{yes}

ts_lexize

-----------

{}

<screen>

ALTER TEXT SEARCH DICTIONARY public.simple_dict ( Accept = false );

ts_lexize

-----------

ts_lexize

-----------

{}

Then we will get these results:

<screen>

mydb=# CREATE TEXT SEARCH DICTIONARY syn (template=synonym, synonyms='synonym_sample');

ts_lexize

-----------

{index}

(1 row)

mydb=# CREATE TEXT SEARCH CONFIGURATION tst (copy=simple);

mydb=# ALTER TEXT SEARCH CONFIGURATION tst ALTER MAPPING FOR asciiword WITH syn;

to_tsvector

-------------

'index':1

(1 row)

to_tsquery

------------

'index':*

'are' 'indexes' 'useful' 'very'

(1 row)

?column?

----------

t

Here is a simple example:

<screen>

alias | description | token | dictionaries | dictionary | lexemes

-----------+-----------------+-------+----------------+--------------+---------

asciiword | Word, all ASCII | a | {english_stem} | english_stem | {}

</programlisting>

<screen>

alias | description | token | dictionaries | dictionary | lexemes

-----------+-----------------+-------------+-------------------------------+----------------+-------------

asciiword | Word, all ASCII | The | {english_ispell,english_stem} | english_ispell | {}

<screen>

SELECT alias, token, dictionary, lexemes

alias | token | dictionary | lexemes

-----------+-------------+----------------+-------------

asciiword | The | english_ispell | {}

where this can be confusing:

<screen>

?column?

----------

t