<synopsis>

<replaceable>database</replaceable><literal>.</literal><replaceable>schema</replaceable><literal>.</literal><replaceable>table</replaceable>

</synopsis>

can be used too, but at present this is just for<foreignphrase>pro

forma</foreignphrase>compliance with the SQL standard. If you write a database name,

can be used too, but at present this is just for pro forma

compliance with the SQL standard. If you write a database name,

it must be the same as the database you are connected to.

</para>

<para>

The <literal>VALID UNTIL</literal> clause defines an expiration time for a

password only, not for the role<foreignphrase>per se</foreignphrase>. In

password only, not for the role per se. In

particular, the expiration time is not enforced when logging in using

a non-password-based authentication method.

</para>

WHERE sl_name = shoelace.sl_name);

</programlisting>

<foreignphrase>Voil&agrave;</foreignphrase>:

The results are:

<programlisting>

SELECT * FROM shoelace;

<productname>PostgreSQL</productname> has an extensible type system that is

more general and flexible than other <acronym>SQL</acronym> implementations.

Hence, most type conversion behavior in <productname>PostgreSQL</productname>

is governed by general rules rather than by<foreignphrase>ad hoc</foreignphrase>

is governed by general rules rather than by ad hoc

heuristics. This allows the use of mixed-type expressions even with

user-defined types.

</para>