Gecko [ finalhopeacademy.com ]

/ usr / share / doc / postgresql-9.2.24 / html / [ HOME SHELL ]

Name	Size	Permission
LEGALNOTICE.html	2.62 KB	-rw-r--r--
acronyms.html	15.9 KB	-rw-r--r--
admin.html	12.27 KB	-rw-r--r--
adminpack.html	7.7 KB	-rw-r--r--
app-clusterdb.html	10.35 KB	-rw-r--r--
app-createdb.html	12.55 KB	-rw-r--r--
app-createlang.html	9.67 KB	-rw-r--r--
app-createuser.html	15.27 KB	-rw-r--r--
app-dropdb.html	9.42 KB	-rw-r--r--
app-droplang.html	9.41 KB	-rw-r--r--
app-dropuser.html	9.37 KB	-rw-r--r--
app-ecpg.html	8.51 KB	-rw-r--r--
app-initdb.html	15.04 KB	-rw-r--r--
app-pg-ctl.html	21.93 KB	-rw-r--r--
app-pg-dumpall.html	20.22 KB	-rw-r--r--
app-pgbasebackup.html	19.37 KB	-rw-r--r--
app-pgconfig.html	10.83 KB	-rw-r--r--
app-pgcontroldata.html	3.89 KB	-rw-r--r--
app-pgdump.html	42.93 KB	-rw-r--r--
app-pgreceivexlog.html	10.8 KB	-rw-r--r--
app-pgresetxlog.html	11.29 KB	-rw-r--r--
app-pgrestore.html	29.56 KB	-rw-r--r--
app-postgres.html	31.08 KB	-rw-r--r--
app-postmaster.html	2.93 KB	-rw-r--r--
app-psql.html	135.62 KB	-rw-r--r--
app-reindexdb.html	11.02 KB	-rw-r--r--
app-vacuumdb.html	12.32 KB	-rw-r--r--
appendixes.html	25.71 KB	-rw-r--r--
applevel-consistency.html	10.07 KB	-rw-r--r--
archive-recovery-settings.html	7.17 KB	-rw-r--r--
arrays.html	27.42 KB	-rw-r--r--
auth-delay.html	3.69 KB	-rw-r--r--
auth-methods.html	35.35 KB	-rw-r--r--
auth-pg-hba-conf.html	29.06 KB	-rw-r--r--
auth-username-maps.html	8.4 KB	-rw-r--r--
auto-explain.html	9.66 KB	-rw-r--r--
backup-dump.html	15.55 KB	-rw-r--r--
backup-file.html	7.81 KB	-rw-r--r--
backup.html	4.38 KB	-rw-r--r--
biblio.html	11.28 KB	-rw-r--r--
bki-commands.html	9.42 KB	-rw-r--r--
bki-example.html	2.98 KB	-rw-r--r--
bki-format.html	3.38 KB	-rw-r--r--
bki-structure.html	4.22 KB	-rw-r--r--
bki.html	4.23 KB	-rw-r--r--
bookindex.html	237.47 KB	-rw-r--r--
btree-gin.html	4.49 KB	-rw-r--r--
btree-gist.html	6.72 KB	-rw-r--r--
bug-reporting.html	18.21 KB	-rw-r--r--
catalog-pg-aggregate.html	5.37 KB	-rw-r--r--
catalog-pg-am.html	10.3 KB	-rw-r--r--
catalog-pg-amop.html	7.42 KB	-rw-r--r--
catalog-pg-amproc.html	4.77 KB	-rw-r--r--
catalog-pg-attrdef.html	4.26 KB	-rw-r--r--
catalog-pg-attribute.html	10.05 KB	-rw-r--r--
catalog-pg-auth-members.html	4.16 KB	-rw-r--r--
catalog-pg-authid.html	6.66 KB	-rw-r--r--
catalog-pg-cast.html	6.79 KB	-rw-r--r--
catalog-pg-class.html	12.36 KB	-rw-r--r--
catalog-pg-collation.html	5.76 KB	-rw-r--r--
catalog-pg-constraint.html	11.31 KB	-rw-r--r--
catalog-pg-conversion.html	4.33 KB	-rw-r--r--
catalog-pg-database.html	6.86 KB	-rw-r--r--
catalog-pg-db-role-setting.htm...	3.97 KB	-rw-r--r--
catalog-pg-default-acl.html	5.14 KB	-rw-r--r--
catalog-pg-depend.html	8.43 KB	-rw-r--r--
catalog-pg-description.html	4.37 KB	-rw-r--r--
catalog-pg-enum.html	4.61 KB	-rw-r--r--
catalog-pg-extension.html	5.16 KB	-rw-r--r--
catalog-pg-foreign-data-wrappe...	4.83 KB	-rw-r--r--
catalog-pg-foreign-server.html	4.58 KB	-rw-r--r--
catalog-pg-foreign-table.html	3.94 KB	-rw-r--r--
catalog-pg-index.html	8.66 KB	-rw-r--r--
catalog-pg-inherits.html	3.8 KB	-rw-r--r--
catalog-pg-language.html	5.81 KB	-rw-r--r--
catalog-pg-largeobject-metadat...	3.54 KB	-rw-r--r--
catalog-pg-largeobject.html	5.03 KB	-rw-r--r--
catalog-pg-namespace.html	3.66 KB	-rw-r--r--
catalog-pg-opclass.html	5.73 KB	-rw-r--r--
catalog-pg-operator.html	6.49 KB	-rw-r--r--
catalog-pg-opfamily.html	4.7 KB	-rw-r--r--
catalog-pg-pltemplate.html	5.24 KB	-rw-r--r--
catalog-pg-proc.html	13.09 KB	-rw-r--r--
catalog-pg-range.html	5.06 KB	-rw-r--r--
catalog-pg-rewrite.html	5.26 KB	-rw-r--r--
catalog-pg-seclabel.html	4.41 KB	-rw-r--r--
catalog-pg-shdepend.html	6.88 KB	-rw-r--r--
catalog-pg-shdescription.html	4.15 KB	-rw-r--r--
catalog-pg-shseclabel.html	4.3 KB	-rw-r--r--
catalog-pg-statistic.html	9.31 KB	-rw-r--r--
catalog-pg-tablespace.html	4.06 KB	-rw-r--r--
catalog-pg-trigger.html	8.09 KB	-rw-r--r--
catalog-pg-ts-config-map.html	4.09 KB	-rw-r--r--
catalog-pg-ts-config.html	4.38 KB	-rw-r--r--
catalog-pg-ts-dict.html	4.61 KB	-rw-r--r--
catalog-pg-ts-parser.html	4.96 KB	-rw-r--r--
catalog-pg-ts-template.html	4.16 KB	-rw-r--r--
catalog-pg-type.html	19.44 KB	-rw-r--r--
catalog-pg-user-mapping.html	3.76 KB	-rw-r--r--
catalogs-overview.html	10.19 KB	-rw-r--r--
catalogs.html	10.14 KB	-rw-r--r--
charset.html	4.06 KB	-rw-r--r--
chkpass.html	4.29 KB	-rw-r--r--
citext.html	10.89 KB	-rw-r--r--
client-authentication-problems...	4.13 KB	-rw-r--r--
client-authentication.html	5.78 KB	-rw-r--r--
client-interfaces.html	13.4 KB	-rw-r--r--
collation.html	13.89 KB	-rw-r--r--
config-setting.html	10.88 KB	-rw-r--r--
connect-estab.html	4.21 KB	-rw-r--r--
continuous-archiving.html	48.66 KB	-rw-r--r--
contrib-dblink-build-sql-delet...	5.32 KB	-rw-r--r--
contrib-dblink-build-sql-inser...	5.91 KB	-rw-r--r--
contrib-dblink-build-sql-updat...	6.13 KB	-rw-r--r--
contrib-dblink-cancel-query.ht...	3.73 KB	-rw-r--r--
contrib-dblink-close.html	4.54 KB	-rw-r--r--
contrib-dblink-connect-u.html	4.38 KB	-rw-r--r--
contrib-dblink-connect.html	7.15 KB	-rw-r--r--
contrib-dblink-disconnect.html	3.63 KB	-rw-r--r--
contrib-dblink-error-message.h...	3.43 KB	-rw-r--r--
contrib-dblink-exec.html	5.34 KB	-rw-r--r--
contrib-dblink-fetch.html	5.84 KB	-rw-r--r--
contrib-dblink-function.html	8.43 KB	-rw-r--r--
contrib-dblink-get-connections...	3.13 KB	-rw-r--r--
contrib-dblink-get-notify.html	4.07 KB	-rw-r--r--
contrib-dblink-get-pkey.html	4.39 KB	-rw-r--r--
contrib-dblink-get-result.html	6.8 KB	-rw-r--r--
contrib-dblink-is-busy.html	3.41 KB	-rw-r--r--
contrib-dblink-open.html	5.34 KB	-rw-r--r--
contrib-dblink-send-query.html	4.07 KB	-rw-r--r--
contrib-prog-client.html	3.35 KB	-rw-r--r--
contrib-prog-server.html	3.75 KB	-rw-r--r--
contrib-prog.html	3.24 KB	-rw-r--r--
contrib-spi.html	10.97 KB	-rw-r--r--
contrib.html	8.7 KB	-rw-r--r--
creating-cluster.html	12.17 KB	-rw-r--r--
cube.html	15.57 KB	-rw-r--r--
database-roles.html	5.95 KB	-rw-r--r--
datatype-binary.html	12.59 KB	-rw-r--r--
datatype-bit.html	4.98 KB	-rw-r--r--
datatype-boolean.html	5.14 KB	-rw-r--r--
datatype-character.html	11.61 KB	-rw-r--r--
datatype-datetime.html	49.57 KB	-rw-r--r--
datatype-enum.html	6.28 KB	-rw-r--r--
datatype-geometric.html	12.21 KB	-rw-r--r--
datatype-json.html	3.36 KB	-rw-r--r--
datatype-money.html	5.35 KB	-rw-r--r--
datatype-net-types.html	10.18 KB	-rw-r--r--
datatype-numeric.html	21.83 KB	-rw-r--r--
datatype-oid.html	9.46 KB	-rw-r--r--
datatype-pseudo.html	7.11 KB	-rw-r--r--
datatype-textsearch.html	9.8 KB	-rw-r--r--
datatype-uuid.html	4.45 KB	-rw-r--r--
datatype-xml.html	11.07 KB	-rw-r--r--
datatype.html	16.22 KB	-rw-r--r--
datetime-appendix.html	3.44 KB	-rw-r--r--
datetime-config-files.html	8.77 KB	-rw-r--r--
datetime-input-rules.html	6.6 KB	-rw-r--r--
datetime-keywords.html	4.98 KB	-rw-r--r--
datetime-units-history.html	7.46 KB	-rw-r--r--
dblink.html	5.2 KB	-rw-r--r--
ddl-alter.html	10.25 KB	-rw-r--r--
ddl-basics.html	7.63 KB	-rw-r--r--
ddl-constraints.html	22.26 KB	-rw-r--r--
ddl-default.html	4.43 KB	-rw-r--r--
ddl-depend.html	6.35 KB	-rw-r--r--
ddl-foreign-data.html	4.38 KB	-rw-r--r--
ddl-inherit.html	14.95 KB	-rw-r--r--
ddl-others.html	3.01 KB	-rw-r--r--
ddl-partitioning.html	27.11 KB	-rw-r--r--
ddl-priv.html	5.92 KB	-rw-r--r--
ddl-schemas.html	17.62 KB	-rw-r--r--
ddl-system-columns.html	7.86 KB	-rw-r--r--
ddl.html	6.23 KB	-rw-r--r--
dict-int.html	4.68 KB	-rw-r--r--
dict-xsyn.html	6.33 KB	-rw-r--r--
different-replication-solution...	14.45 KB	-rw-r--r--
disk-full.html	3.43 KB	-rw-r--r--
disk-usage.html	5.53 KB	-rw-r--r--
diskusage.html	2.61 KB	-rw-r--r--
dml-delete.html	3.48 KB	-rw-r--r--
dml-insert.html	5.67 KB	-rw-r--r--
dml-returning.html	4.98 KB	-rw-r--r--
dml-update.html	5.43 KB	-rw-r--r--
dml.html	2.88 KB	-rw-r--r--
docguide-authoring.html	6.6 KB	-rw-r--r--
docguide-build.html	14.92 KB	-rw-r--r--
docguide-docbook.html	3.76 KB	-rw-r--r--
docguide-style.html	7.25 KB	-rw-r--r--
docguide-toolsets.html	20.2 KB	-rw-r--r--
docguide.html	3.54 KB	-rw-r--r--
dummy-seclabel.html	4.26 KB	-rw-r--r--
dynamic-trace.html	26.6 KB	-rw-r--r--
earthdistance.html	8.6 KB	-rw-r--r--
ecpg-commands.html	9.3 KB	-rw-r--r--
ecpg-concept.html	4.86 KB	-rw-r--r--
ecpg-connect.html	10.57 KB	-rw-r--r--
ecpg-cpp.html	9.4 KB	-rw-r--r--
ecpg-descriptors.html	34.09 KB	-rw-r--r--
ecpg-develop.html	7.78 KB	-rw-r--r--
ecpg-dynamic.html	6.36 KB	-rw-r--r--
ecpg-errors.html	25.13 KB	-rw-r--r--
ecpg-informix-compat.html	51.52 KB	-rw-r--r--
ecpg-library.html	5.66 KB	-rw-r--r--
ecpg-lo.html	5.4 KB	-rw-r--r--
ecpg-pgtypes.html	53.18 KB	-rw-r--r--
ecpg-preproc.html	8.77 KB	-rw-r--r--
ecpg-process.html	5.26 KB	-rw-r--r--
ecpg-sql-allocate-descriptor.h...	3.89 KB	-rw-r--r--
ecpg-sql-commands.html	4.59 KB	-rw-r--r--
ecpg-sql-connect.html	9.16 KB	-rw-r--r--
ecpg-sql-deallocate-descriptor...	3.68 KB	-rw-r--r--
ecpg-sql-declare.html	5.27 KB	-rw-r--r--
ecpg-sql-describe.html	4.49 KB	-rw-r--r--
ecpg-sql-disconnect.html	4.62 KB	-rw-r--r--
ecpg-sql-execute-immediate.htm...	3.79 KB	-rw-r--r--
ecpg-sql-get-descriptor.html	7.53 KB	-rw-r--r--
ecpg-sql-open.html	4.53 KB	-rw-r--r--
ecpg-sql-prepare.html	4.08 KB	-rw-r--r--
ecpg-sql-set-autocommit.html	3.25 KB	-rw-r--r--
ecpg-sql-set-connection.html	3.84 KB	-rw-r--r--
ecpg-sql-set-descriptor.html	5.38 KB	-rw-r--r--
ecpg-sql-type.html	4.91 KB	-rw-r--r--
ecpg-sql-var.html	3.46 KB	-rw-r--r--
ecpg-sql-whenever.html	4.58 KB	-rw-r--r--
ecpg-variables.html	39.34 KB	-rw-r--r--
ecpg.html	10.1 KB	-rw-r--r--
encryption-options.html	7.32 KB	-rw-r--r--
errcodes-appendix.html	36.1 KB	-rw-r--r--
error-message-reporting.html	13.79 KB	-rw-r--r--
error-style-guide.html	16.38 KB	-rw-r--r--
event-log-registration.html	4.09 KB	-rw-r--r--
executor.html	6.46 KB	-rw-r--r--
explicit-joins.html	10.76 KB	-rw-r--r--
explicit-locking.html	24.49 KB	-rw-r--r--
extend-extensions.html	31.67 KB	-rw-r--r--
extend-how.html	4.45 KB	-rw-r--r--
extend-pgxs.html	11.49 KB	-rw-r--r--
extend-type-system.html	9.87 KB	-rw-r--r--
extend.html	9.75 KB	-rw-r--r--
external-admin-tools.html	2.66 KB	-rw-r--r--
external-extensions.html	3.19 KB	-rw-r--r--
external-interfaces.html	5.38 KB	-rw-r--r--
external-pl.html	4.56 KB	-rw-r--r--
external-projects.html	2.93 KB	-rw-r--r--
fdw-callbacks.html	12.6 KB	-rw-r--r--
fdw-functions.html	4.39 KB	-rw-r--r--
fdw-helpers.html	5.85 KB	-rw-r--r--
fdw-planning.html	9.61 KB	-rw-r--r--
fdwhandler.html	3.9 KB	-rw-r--r--
features-sql-standard.html	38.19 KB	-rw-r--r--
features.html	7.39 KB	-rw-r--r--
file-fdw.html	7.53 KB	-rw-r--r--
functions-admin.html	49.21 KB	-rw-r--r--
functions-aggregate.html	21.3 KB	-rw-r--r--
functions-array.html	13.2 KB	-rw-r--r--
functions-binarystring.html	12.29 KB	-rw-r--r--
functions-bitstring.html	6.63 KB	-rw-r--r--
functions-comparison.html	10.39 KB	-rw-r--r--
functions-comparisons.html	13.21 KB	-rw-r--r--
functions-conditional.html	10.75 KB	-rw-r--r--
functions-datetime.html	47.17 KB	-rw-r--r--
functions-enum.html	5.36 KB	-rw-r--r--
functions-formatting.html	34.57 KB	-rw-r--r--
functions-geometry.html	19.87 KB	-rw-r--r--
functions-info.html	57.28 KB	-rw-r--r--
functions-json.html	3.72 KB	-rw-r--r--
functions-logical.html	4.56 KB	-rw-r--r--
functions-matching.html	73.95 KB	-rw-r--r--
functions-math.html	19.92 KB	-rw-r--r--
functions-net.html	13.19 KB	-rw-r--r--
functions-range.html	10.6 KB	-rw-r--r--
functions-sequence.html	12.62 KB	-rw-r--r--
functions-srf.html	8.63 KB	-rw-r--r--
functions-string.html	57.67 KB	-rw-r--r--
functions-subquery.html	16 KB	-rw-r--r--
functions-textsearch.html	20.01 KB	-rw-r--r--
functions-trigger.html	4.44 KB	-rw-r--r--
functions-window.html	11.8 KB	-rw-r--r--
functions-xml.html	31.42 KB	-rw-r--r--
functions.html	9.71 KB	-rw-r--r--
fuzzystrmatch.html	7.87 KB	-rw-r--r--
geqo-biblio.html	3.38 KB	-rw-r--r--
geqo-intro.html	4.31 KB	-rw-r--r--
geqo-intro2.html	5.5 KB	-rw-r--r--
geqo-pg-intro.html	8.58 KB	-rw-r--r--
geqo.html	3.53 KB	-rw-r--r--
gin-examples.html	3.24 KB	-rw-r--r--
gin-extensibility.html	14.06 KB	-rw-r--r--
gin-implementation.html	6.41 KB	-rw-r--r--
gin-intro.html	4.55 KB	-rw-r--r--
gin-limit.html	2.75 KB	-rw-r--r--
gin-tips.html	5.58 KB	-rw-r--r--
gin.html	2.86 KB	-rw-r--r--
gist-examples.html	3.66 KB	-rw-r--r--
gist-extensibility.html	23.78 KB	-rw-r--r--
gist-implementation.html	4 KB	-rw-r--r--
gist-intro.html	3.53 KB	-rw-r--r--
gist.html	2.62 KB	-rw-r--r--
git.html	4.46 KB	-rw-r--r--
high-availability.html	7.52 KB	-rw-r--r--
history.html	11.64 KB	-rw-r--r--
hot-standby.html	35.2 KB	-rw-r--r--
hstore.html	22.1 KB	-rw-r--r--
index-catalog.html	7.81 KB	-rw-r--r--
index-cost-estimation.html	9.76 KB	-rw-r--r--
index-functions.html	18.67 KB	-rw-r--r--
index-locking.html	7.86 KB	-rw-r--r--
index-scanning.html	10.46 KB	-rw-r--r--
index-unique-checks.html	8.98 KB	-rw-r--r--
index.html	7.88 KB	-rw-r--r--
indexam.html	5.12 KB	-rw-r--r--
indexes-bitmap-scans.html	6.43 KB	-rw-r--r--
indexes-collations.html	3.55 KB	-rw-r--r--
indexes-examine.html	6.99 KB	-rw-r--r--
indexes-expressional.html	4.7 KB	-rw-r--r--
indexes-intro.html	6.17 KB	-rw-r--r--
indexes-multicolumn.html	6.15 KB	-rw-r--r--
indexes-opclass.html	7.16 KB	-rw-r--r--
indexes-ordering.html	6.33 KB	-rw-r--r--
indexes-partial.html	11.54 KB	-rw-r--r--
indexes-types.html	9.99 KB	-rw-r--r--
indexes-unique.html	3.91 KB	-rw-r--r--
indexes.html	3.53 KB	-rw-r--r--
information-schema.html	10.92 KB	-rw-r--r--
infoschema-administrable-role-...	3.66 KB	-rw-r--r--
infoschema-applicable-roles.ht...	3.88 KB	-rw-r--r--
infoschema-attributes.html	12.51 KB	-rw-r--r--
infoschema-character-sets.html	6.88 KB	-rw-r--r--
infoschema-check-constraint-ro...	4.25 KB	-rw-r--r--
infoschema-check-constraints.h...	3.79 KB	-rw-r--r--
infoschema-collation-character...	4.32 KB	-rw-r--r--
infoschema-collations.html	3.79 KB	-rw-r--r--
infoschema-column-domain-usage...	4.22 KB	-rw-r--r--
infoschema-column-options.html	4.01 KB	-rw-r--r--
infoschema-column-privileges.h...	4.91 KB	-rw-r--r--
infoschema-column-udt-usage.ht...	4.48 KB	-rw-r--r--
infoschema-columns.html	17.21 KB	-rw-r--r--
infoschema-constraint-column-u...	4.76 KB	-rw-r--r--
infoschema-constraint-table-us...	4.66 KB	-rw-r--r--
infoschema-data-type-privilege...	4.97 KB	-rw-r--r--
infoschema-datatypes.html	4.13 KB	-rw-r--r--
infoschema-domain-constraints....	4.55 KB	-rw-r--r--
infoschema-domain-udt-usage.ht...	4.07 KB	-rw-r--r--
infoschema-domains.html	11.1 KB	-rw-r--r--
infoschema-element-types.html	11.11 KB	-rw-r--r--
infoschema-enabled-roles.html	3.69 KB	-rw-r--r--
infoschema-foreign-data-wrappe...	3.82 KB	-rw-r--r--
infoschema-foreign-data-wrappe...	4.13 KB	-rw-r--r--
infoschema-foreign-server-opti...	3.76 KB	-rw-r--r--
infoschema-foreign-servers.htm...	4.46 KB	-rw-r--r--
infoschema-foreign-table-optio...	3.88 KB	-rw-r--r--
infoschema-foreign-tables.html	3.98 KB	-rw-r--r--
infoschema-information-schema-...	3.28 KB	-rw-r--r--
infoschema-key-column-usage.ht...	5.06 KB	-rw-r--r--
infoschema-parameters.html	10.55 KB	-rw-r--r--
infoschema-referential-constra...	5.53 KB	-rw-r--r--
infoschema-role-column-grants....	4.9 KB	-rw-r--r--
infoschema-role-routine-grants...	5.23 KB	-rw-r--r--
infoschema-role-table-grants.h...	5.3 KB	-rw-r--r--
infoschema-role-udt-grants.htm...	4.67 KB	-rw-r--r--
infoschema-role-usage-grants.h...	4.89 KB	-rw-r--r--
infoschema-routine-privileges....	4.91 KB	-rw-r--r--
infoschema-routines.html	22.51 KB	-rw-r--r--
infoschema-schema.html	3.11 KB	-rw-r--r--
infoschema-schemata.html	4.15 KB	-rw-r--r--
infoschema-sequences.html	5.97 KB	-rw-r--r--
infoschema-sql-features.html	4.6 KB	-rw-r--r--
infoschema-sql-implementation-...	4.4 KB	-rw-r--r--
infoschema-sql-languages.html	4.97 KB	-rw-r--r--
infoschema-sql-packages.html	4.08 KB	-rw-r--r--
infoschema-sql-parts.html	3.98 KB	-rw-r--r--
infoschema-sql-sizing-profiles...	4.08 KB	-rw-r--r--
infoschema-sql-sizing.html	4 KB	-rw-r--r--
infoschema-table-constraints.h...	4.8 KB	-rw-r--r--
infoschema-table-privileges.ht...	4.98 KB	-rw-r--r--
infoschema-tables.html	5.82 KB	-rw-r--r--
infoschema-triggered-update-co...	4.45 KB	-rw-r--r--
infoschema-triggers.html	9.23 KB	-rw-r--r--
infoschema-udt-privileges.html	4.4 KB	-rw-r--r--
infoschema-usage-privileges.ht...	5.38 KB	-rw-r--r--
infoschema-user-defined-types....	9.52 KB	-rw-r--r--
infoschema-user-mapping-option...	4.34 KB	-rw-r--r--
infoschema-user-mappings.html	3.74 KB	-rw-r--r--
infoschema-view-column-usage.h...	4.62 KB	-rw-r--r--
infoschema-view-routine-usage....	4.27 KB	-rw-r--r--
infoschema-view-table-usage.ht...	4.29 KB	-rw-r--r--
infoschema-views.html	5.4 KB	-rw-r--r--
install-getsource.html	3.49 KB	-rw-r--r--
install-post.html	7.89 KB	-rw-r--r--
install-procedure.html	45.44 KB	-rw-r--r--
install-requirements.html	14.14 KB	-rw-r--r--
install-short.html	2.8 KB	-rw-r--r--
install-windows-full.html	18.82 KB	-rw-r--r--
install-windows-libpq.html	6.14 KB	-rw-r--r--
install-windows.html	6.46 KB	-rw-r--r--
installation-platform-notes.ht...	38.46 KB	-rw-r--r--
installation.html	4.06 KB	-rw-r--r--
intagg.html	6.11 KB	-rw-r--r--
intarray.html	13.43 KB	-rw-r--r--
internals.html	15.27 KB	-rw-r--r--
intro-whatis.html	3.92 KB	-rw-r--r--
isn.html	13.04 KB	-rw-r--r--
kernel-resources.html	36.94 KB	-rw-r--r--
largeobjects.html	4.57 KB	-rw-r--r--
libpq-async.html	20.53 KB	-rw-r--r--
libpq-build.html	6.22 KB	-rw-r--r--
libpq-cancel.html	6.62 KB	-rw-r--r--
libpq-connect.html	50.05 KB	-rw-r--r--
libpq-control.html	6.13 KB	-rw-r--r--
libpq-copy.html	21.92 KB	-rw-r--r--
libpq-envars.html	9.59 KB	-rw-r--r--
libpq-events.html	22.55 KB	-rw-r--r--
libpq-example.html	15.65 KB	-rw-r--r--
libpq-exec.html	63.36 KB	-rw-r--r--
libpq-fastpath.html	5.98 KB	-rw-r--r--
libpq-ldap.html	5.38 KB	-rw-r--r--
libpq-misc.html	13.49 KB	-rw-r--r--
libpq-notice-processing.html	6.14 KB	-rw-r--r--
libpq-notify.html	6.56 KB	-rw-r--r--
libpq-pgpass.html	4.75 KB	-rw-r--r--
libpq-pgservice.html	3.81 KB	-rw-r--r--
libpq-single-row-mode.html	6.2 KB	-rw-r--r--
libpq-ssl.html	19.5 KB	-rw-r--r--
libpq-status.html	17.28 KB	-rw-r--r--
libpq-threading.html	5.41 KB	-rw-r--r--
libpq.html	7.73 KB	-rw-r--r--
lo-examplesect.html	8.49 KB	-rw-r--r--
lo-funcs.html	4.53 KB	-rw-r--r--
lo-implementation.html	3.27 KB	-rw-r--r--
lo-interfaces.html	14.8 KB	-rw-r--r--
lo-intro.html	3.13 KB	-rw-r--r--
lo.html	6.47 KB	-rw-r--r--
locale.html	13.37 KB	-rw-r--r--
locking-indexes.html	4.25 KB	-rw-r--r--
log-shipping-alternative.html	10.8 KB	-rw-r--r--
logfile-maintenance.html	6.98 KB	-rw-r--r--
ltree.html	26.66 KB	-rw-r--r--
maintenance.html	5.41 KB	-rw-r--r--
manage-ag-config.html	3.66 KB	-rw-r--r--
manage-ag-createdb.html	6.16 KB	-rw-r--r--
manage-ag-dropdb.html	3.52 KB	-rw-r--r--
manage-ag-overview.html	5.02 KB	-rw-r--r--
manage-ag-tablespaces.html	9.03 KB	-rw-r--r--
manage-ag-templatedbs.html	7.97 KB	-rw-r--r--
managing-databases.html	3.2 KB	-rw-r--r--
monitoring-locks.html	3.59 KB	-rw-r--r--
monitoring-ps.html	6.62 KB	-rw-r--r--
monitoring-stats.html	56.7 KB	-rw-r--r--
monitoring.html	4.35 KB	-rw-r--r--
multibyte.html	31.22 KB	-rw-r--r--
mvcc-caveats.html	3.98 KB	-rw-r--r--
mvcc-intro.html	4.45 KB	-rw-r--r--
mvcc.html	4.2 KB	-rw-r--r--
nls-programmer.html	9.84 KB	-rw-r--r--
nls-translator.html	14.18 KB	-rw-r--r--
nls.html	3.06 KB	-rw-r--r--
non-durability.html	4.38 KB	-rw-r--r--
notation.html	4.31 KB	-rw-r--r--
oid2name.html	11.68 KB	-rw-r--r--
overview.html	4 KB	-rw-r--r--
pageinspect.html	7.93 KB	-rw-r--r--
parser-stage.html	7.93 KB	-rw-r--r--
passwordcheck.html	4.68 KB	-rw-r--r--
performance-tips.html	4.4 KB	-rw-r--r--
perm-functions.html	3.26 KB	-rw-r--r--
pgarchivecleanup.html	8.79 KB	-rw-r--r--
pgbench.html	30.11 KB	-rw-r--r--
pgbuffercache.html	7.53 KB	-rw-r--r--
pgcrypto.html	37.89 KB	-rw-r--r--
pgfreespacemap.html	5.11 KB	-rw-r--r--
pgrowlocks.html	5.94 KB	-rw-r--r--
pgstandby.html	14.85 KB	-rw-r--r--
pgstatstatements.html	15.69 KB	-rw-r--r--
pgstattuple.html	9.23 KB	-rw-r--r--
pgtestfsync.html	5.13 KB	-rw-r--r--
pgtesttiming.html	12.18 KB	-rw-r--r--
pgtrgm.html	12.04 KB	-rw-r--r--
pgupgrade.html	24.16 KB	-rw-r--r--
planner-optimizer.html	9.18 KB	-rw-r--r--
planner-stats-details.html	3.2 KB	-rw-r--r--
planner-stats-security.html	5.43 KB	-rw-r--r--
planner-stats.html	8.85 KB	-rw-r--r--
plhandler.html	13.43 KB	-rw-r--r--
plperl-builtins.html	17.85 KB	-rw-r--r--
plperl-data.html	2.81 KB	-rw-r--r--
plperl-funcs.html	13.06 KB	-rw-r--r--
plperl-global.html	4.95 KB	-rw-r--r--
plperl-triggers.html	6.29 KB	-rw-r--r--
plperl-trusted.html	6.55 KB	-rw-r--r--
plperl-under-the-hood.html	8.78 KB	-rw-r--r--
plperl.html	4.81 KB	-rw-r--r--
plpgsql-control-structures.htm...	45.1 KB	-rw-r--r--
plpgsql-cursors.html	24.99 KB	-rw-r--r--
plpgsql-declarations.html	21.24 KB	-rw-r--r--
plpgsql-development-tips.html	9.29 KB	-rw-r--r--
plpgsql-errors-and-messages.ht...	9.86 KB	-rw-r--r--
plpgsql-expressions.html	4.55 KB	-rw-r--r--
plpgsql-implementation.html	17.62 KB	-rw-r--r--
plpgsql-overview.html	8.82 KB	-rw-r--r--
plpgsql-porting.html	26.46 KB	-rw-r--r--
plpgsql-statements.html	31.47 KB	-rw-r--r--
plpgsql-structure.html	8.13 KB	-rw-r--r--
plpgsql-trigger.html	21.8 KB	-rw-r--r--
plpgsql.html	6.8 KB	-rw-r--r--
plpython-data.html	14.3 KB	-rw-r--r--
plpython-database.html	15.05 KB	-rw-r--r--
plpython-do.html	2.71 KB	-rw-r--r--
plpython-envar.html	3.79 KB	-rw-r--r--
plpython-funcs.html	5.35 KB	-rw-r--r--
plpython-python23.html	7.04 KB	-rw-r--r--
plpython-sharing.html	2.96 KB	-rw-r--r--
plpython-subtransaction.html	7.7 KB	-rw-r--r--
plpython-trigger.html	4.95 KB	-rw-r--r--
plpython-util.html	4.98 KB	-rw-r--r--
plpython.html	5.92 KB	-rw-r--r--
pltcl-data.html	2.84 KB	-rw-r--r--
pltcl-dbaccess.html	13.58 KB	-rw-r--r--
pltcl-functions.html	6.03 KB	-rw-r--r--
pltcl-global.html	4.95 KB	-rw-r--r--
pltcl-overview.html	5.16 KB	-rw-r--r--
pltcl-procnames.html	3.15 KB	-rw-r--r--
pltcl-trigger.html	9.23 KB	-rw-r--r--
pltcl-unknown.html	4.96 KB	-rw-r--r--
pltcl.html	3.32 KB	-rw-r--r--
populate.html	16.71 KB	-rw-r--r--
postgres-user.html	3.24 KB	-rw-r--r--
preface.html	4.95 KB	-rw-r--r--
preventing-server-spoofing.htm...	4.5 KB	-rw-r--r--
protocol-changes.html	6.49 KB	-rw-r--r--
protocol-error-fields.html	5.99 KB	-rw-r--r--
protocol-flow.html	45.12 KB	-rw-r--r--
protocol-message-formats.html	39.89 KB	-rw-r--r--
protocol-message-types.html	4.82 KB	-rw-r--r--
protocol-overview.html	9.44 KB	-rw-r--r--
protocol-replication.html	14.32 KB	-rw-r--r--
protocol.html	5.52 KB	-rw-r--r--
queries-limit.html	5.21 KB	-rw-r--r--
queries-order.html	7.2 KB	-rw-r--r--
queries-overview.html	4.95 KB	-rw-r--r--
queries-select-lists.html	9.09 KB	-rw-r--r--
queries-table-expressions.html	38.94 KB	-rw-r--r--
queries-union.html	4.99 KB	-rw-r--r--
queries-values.html	4.81 KB	-rw-r--r--
queries-with.html	20.39 KB	-rw-r--r--
queries.html	4.31 KB	-rw-r--r--
query-path.html	5.34 KB	-rw-r--r--
querytree.html	10.88 KB	-rw-r--r--
rangetypes.html	22.2 KB	-rw-r--r--
recovery-config.html	3.47 KB	-rw-r--r--
recovery-target-settings.html	7.58 KB	-rw-r--r--
reference-client.html	5.96 KB	-rw-r--r--
reference-server.html	3.87 KB	-rw-r--r--
reference.html	22.62 KB	-rw-r--r--
regress-coverage.html	3.25 KB	-rw-r--r--
regress-evaluation.html	12.19 KB	-rw-r--r--
regress-run.html	13.39 KB	-rw-r--r--
regress-variant.html	7.01 KB	-rw-r--r--
regress.html	4.18 KB	-rw-r--r--
release-0-01.html	2.5 KB	-rw-r--r--
release-0-02.html	4.19 KB	-rw-r--r--
release-0-03.html	7.62 KB	-rw-r--r--
release-1-0.html	4.13 KB	-rw-r--r--
release-1-01.html	9.13 KB	-rw-r--r--
release-1-02.html	6.34 KB	-rw-r--r--
release-1-09.html	2.47 KB	-rw-r--r--
release-6-0.html	7.73 KB	-rw-r--r--
release-6-1-1.html	3.63 KB	-rw-r--r--
release-6-1.html	8.81 KB	-rw-r--r--
release-6-2-1.html	4.3 KB	-rw-r--r--
release-6-2.html	8.67 KB	-rw-r--r--
release-6-3-1.html	4.34 KB	-rw-r--r--
release-6-3-2.html	4.06 KB	-rw-r--r--
release-6-3.html	15.93 KB	-rw-r--r--
release-6-4-1.html	3.97 KB	-rw-r--r--
release-6-4-2.html	2.84 KB	-rw-r--r--
release-6-4.html	14.39 KB	-rw-r--r--
release-6-5-1.html	3.75 KB	-rw-r--r--
release-6-5-2.html	4.01 KB	-rw-r--r--
release-6-5-3.html	2.98 KB	-rw-r--r--
release-6-5.html	16.98 KB	-rw-r--r--
release-7-0-1.html	3.83 KB	-rw-r--r--
release-7-0-2.html	2.82 KB	-rw-r--r--
release-7-0-3.html	4.55 KB	-rw-r--r--
release-7-0.html	22.56 KB	-rw-r--r--
release-7-1-1.html	3.19 KB	-rw-r--r--
release-7-1-2.html	2.91 KB	-rw-r--r--
release-7-1-3.html	3.07 KB	-rw-r--r--
release-7-1.html	12.71 KB	-rw-r--r--
release-7-2-1.html	3.92 KB	-rw-r--r--
release-7-2-2.html	3.7 KB	-rw-r--r--
release-7-2-3.html	3.29 KB	-rw-r--r--
release-7-2-4.html	3.5 KB	-rw-r--r--
release-7-2-5.html	3.66 KB	-rw-r--r--
release-7-2-6.html	3.54 KB	-rw-r--r--
release-7-2-7.html	3.64 KB	-rw-r--r--
release-7-2-8.html	3.86 KB	-rw-r--r--
release-7-2.html	26.46 KB	-rw-r--r--
release-7-3-1.html	4.07 KB	-rw-r--r--
release-7-3-10.html	7.32 KB	-rw-r--r--
release-7-3-11.html	4.01 KB	-rw-r--r--
release-7-3-12.html	3.44 KB	-rw-r--r--
release-7-3-13.html	4.51 KB	-rw-r--r--
release-7-3-14.html	3.84 KB	-rw-r--r--
release-7-3-15.html	6.17 KB	-rw-r--r--
release-7-3-16.html	3.34 KB	-rw-r--r--
release-7-3-17.html	3.47 KB	-rw-r--r--
release-7-3-18.html	3.56 KB	-rw-r--r--
release-7-3-19.html	3.6 KB	-rw-r--r--
release-7-3-2.html	5.08 KB	-rw-r--r--
release-7-3-20.html	3.44 KB	-rw-r--r--
release-7-3-21.html	6.07 KB	-rw-r--r--
release-7-3-3.html	10.05 KB	-rw-r--r--
release-7-3-4.html	3.42 KB	-rw-r--r--
release-7-3-5.html	4.39 KB	-rw-r--r--
release-7-3-6.html	4.32 KB	-rw-r--r--
release-7-3-7.html	3.27 KB	-rw-r--r--
release-7-3-8.html	3.49 KB	-rw-r--r--
release-7-3-9.html	3.98 KB	-rw-r--r--
release-7-3.html	32.28 KB	-rw-r--r--
release-7-4-1.html	6.95 KB	-rw-r--r--
release-7-4-10.html	3.72 KB	-rw-r--r--
release-7-4-11.html	4.74 KB	-rw-r--r--
release-7-4-12.html	4.12 KB	-rw-r--r--
release-7-4-13.html	6.8 KB	-rw-r--r--
release-7-4-14.html	3.59 KB	-rw-r--r--
release-7-4-15.html	4.17 KB	-rw-r--r--
release-7-4-16.html	3.88 KB	-rw-r--r--
release-7-4-17.html	3.92 KB	-rw-r--r--
release-7-4-18.html	3.83 KB	-rw-r--r--
release-7-4-19.html	7.07 KB	-rw-r--r--
release-7-4-2.html	8.07 KB	-rw-r--r--
release-7-4-20.html	6.45 KB	-rw-r--r--
release-7-4-21.html	3.83 KB	-rw-r--r--
release-7-4-22.html	3.98 KB	-rw-r--r--
release-7-4-23.html	4.32 KB	-rw-r--r--
release-7-4-24.html	4.19 KB	-rw-r--r--
release-7-4-25.html	4.4 KB	-rw-r--r--
release-7-4-26.html	5.33 KB	-rw-r--r--
release-7-4-27.html	5.04 KB	-rw-r--r--
release-7-4-28.html	5.5 KB	-rw-r--r--
release-7-4-29.html	6.8 KB	-rw-r--r--
release-7-4-3.html	4.51 KB	-rw-r--r--
release-7-4-30.html	6.07 KB	-rw-r--r--
release-7-4-4.html	3.99 KB	-rw-r--r--
release-7-4-5.html	3.12 KB	-rw-r--r--
release-7-4-6.html	4.62 KB	-rw-r--r--
release-7-4-7.html	4.17 KB	-rw-r--r--
release-7-4-8.html	9.92 KB	-rw-r--r--
release-7-4-9.html	5 KB	-rw-r--r--
release-7-4.html	56.03 KB	-rw-r--r--
release-8-0-1.html	4.63 KB	-rw-r--r--
release-8-0-10.html	4.64 KB	-rw-r--r--
release-8-0-11.html	3.88 KB	-rw-r--r--
release-8-0-12.html	3.06 KB	-rw-r--r--
release-8-0-13.html	4.02 KB	-rw-r--r--
release-8-0-14.html	4.41 KB	-rw-r--r--
release-8-0-15.html	8.89 KB	-rw-r--r--
release-8-0-16.html	8.74 KB	-rw-r--r--
release-8-0-17.html	3.83 KB	-rw-r--r--
release-8-0-18.html	5.45 KB	-rw-r--r--
release-8-0-19.html	4.86 KB	-rw-r--r--
release-8-0-2.html	9.34 KB	-rw-r--r--
release-8-0-20.html	4.21 KB	-rw-r--r--
release-8-0-21.html	4.4 KB	-rw-r--r--
release-8-0-22.html	6.29 KB	-rw-r--r--
release-8-0-23.html	5.88 KB	-rw-r--r--
release-8-0-24.html	6.84 KB	-rw-r--r--
release-8-0-25.html	7.25 KB	-rw-r--r--
release-8-0-26.html	7.84 KB	-rw-r--r--
release-8-0-3.html	7.25 KB	-rw-r--r--
release-8-0-4.html	6.52 KB	-rw-r--r--
release-8-0-5.html	4.7 KB	-rw-r--r--
release-8-0-6.html	5.56 KB	-rw-r--r--
release-8-0-7.html	5.77 KB	-rw-r--r--
release-8-0-8.html	7.06 KB	-rw-r--r--
release-8-0-9.html	4.21 KB	-rw-r--r--
release-8-0.html	65.25 KB	-rw-r--r--
release-8-1-1.html	5.33 KB	-rw-r--r--
release-8-1-10.html	4.67 KB	-rw-r--r--
release-8-1-11.html	9.71 KB	-rw-r--r--
release-8-1-12.html	9.12 KB	-rw-r--r--
release-8-1-13.html	4.19 KB	-rw-r--r--
release-8-1-14.html	6.74 KB	-rw-r--r--
release-8-1-15.html	6.13 KB	-rw-r--r--
release-8-1-16.html	5.15 KB	-rw-r--r--
release-8-1-17.html	5.89 KB	-rw-r--r--
release-8-1-18.html	6.29 KB	-rw-r--r--
release-8-1-19.html	6.46 KB	-rw-r--r--
release-8-1-2.html	6.19 KB	-rw-r--r--
release-8-1-20.html	7.13 KB	-rw-r--r--
release-8-1-21.html	7.04 KB	-rw-r--r--
release-8-1-22.html	8.13 KB	-rw-r--r--
release-8-1-23.html	7.75 KB	-rw-r--r--
release-8-1-3.html	6.86 KB	-rw-r--r--
release-8-1-4.html	8.67 KB	-rw-r--r--
release-8-1-5.html	5.35 KB	-rw-r--r--
release-8-1-6.html	5.21 KB	-rw-r--r--
release-8-1-7.html	4.45 KB	-rw-r--r--
release-8-1-8.html	3.04 KB	-rw-r--r--
release-8-1-9.html	4.29 KB	-rw-r--r--
release-8-1.html	60.66 KB	-rw-r--r--
release-8-2-1.html	4.95 KB	-rw-r--r--
release-8-2-10.html	7.99 KB	-rw-r--r--
release-8-2-11.html	6.98 KB	-rw-r--r--
release-8-2-12.html	6.59 KB	-rw-r--r--
release-8-2-13.html	7.18 KB	-rw-r--r--
release-8-2-14.html	7.69 KB	-rw-r--r--
release-8-2-15.html	7.96 KB	-rw-r--r--
release-8-2-16.html	9.08 KB	-rw-r--r--
release-8-2-17.html	8.02 KB	-rw-r--r--
release-8-2-18.html	10.04 KB	-rw-r--r--
release-8-2-19.html	8.39 KB	-rw-r--r--
release-8-2-2.html	5.67 KB	-rw-r--r--
release-8-2-20.html	6.1 KB	-rw-r--r--
release-8-2-21.html	5.46 KB	-rw-r--r--
release-8-2-22.html	9.39 KB	-rw-r--r--
release-8-2-23.html	9.33 KB	-rw-r--r--
release-8-2-3.html	3.02 KB	-rw-r--r--
release-8-2-4.html	5.3 KB	-rw-r--r--
release-8-2-5.html	5.85 KB	-rw-r--r--
release-8-2-6.html	10.3 KB	-rw-r--r--
release-8-2-7.html	9.09 KB	-rw-r--r--
release-8-2-8.html	7.34 KB	-rw-r--r--
release-8-2-9.html	4.18 KB	-rw-r--r--
release-8-2.html	67.77 KB	-rw-r--r--
release-8-3-1.html	10.34 KB	-rw-r--r--
release-8-3-10.html	10.47 KB	-rw-r--r--
release-8-3-11.html	8.75 KB	-rw-r--r--
release-8-3-12.html	11.83 KB	-rw-r--r--
release-8-3-13.html	9.28 KB	-rw-r--r--
release-8-3-14.html	6.1 KB	-rw-r--r--
release-8-3-15.html	6.23 KB	-rw-r--r--
release-8-3-16.html	10.76 KB	-rw-r--r--
release-8-3-17.html	10.34 KB	-rw-r--r--
release-8-3-18.html	11 KB	-rw-r--r--
release-8-3-19.html	8.27 KB	-rw-r--r--
release-8-3-2.html	11.92 KB	-rw-r--r--
release-8-3-20.html	9.03 KB	-rw-r--r--
release-8-3-21.html	4.92 KB	-rw-r--r--
release-8-3-22.html	10.34 KB	-rw-r--r--
release-8-3-23.html	6.14 KB	-rw-r--r--
release-8-3-3.html	4.17 KB	-rw-r--r--
release-8-3-4.html	11.01 KB	-rw-r--r--
release-8-3-5.html	8.49 KB	-rw-r--r--
release-8-3-6.html	8.98 KB	-rw-r--r--
release-8-3-7.html	9.5 KB	-rw-r--r--
release-8-3-8.html	9.04 KB	-rw-r--r--
release-8-3-9.html	9.97 KB	-rw-r--r--
release-8-3.html	68.14 KB	-rw-r--r--
release-8-4-1.html	9.34 KB	-rw-r--r--
release-8-4-10.html	11.65 KB	-rw-r--r--
release-8-4-11.html	13.46 KB	-rw-r--r--
release-8-4-12.html	9.75 KB	-rw-r--r--
release-8-4-13.html	9.49 KB	-rw-r--r--
release-8-4-14.html	5 KB	-rw-r--r--
release-8-4-15.html	10.38 KB	-rw-r--r--
release-8-4-16.html	7.16 KB	-rw-r--r--
release-8-4-17.html	9.35 KB	-rw-r--r--
release-8-4-18.html	6.88 KB	-rw-r--r--
release-8-4-19.html	7.6 KB	-rw-r--r--
release-8-4-2.html	15.33 KB	-rw-r--r--
release-8-4-20.html	15.88 KB	-rw-r--r--
release-8-4-21.html	5.32 KB	-rw-r--r--
release-8-4-22.html	11.04 KB	-rw-r--r--
release-8-4-3.html	13.6 KB	-rw-r--r--
release-8-4-4.html	10.48 KB	-rw-r--r--
release-8-4-5.html	15.56 KB	-rw-r--r--
release-8-4-6.html	10.19 KB	-rw-r--r--
release-8-4-7.html	6.07 KB	-rw-r--r--
release-8-4-8.html	8.64 KB	-rw-r--r--
release-8-4-9.html	14.19 KB	-rw-r--r--
release-8-4.html	85.91 KB	-rw-r--r--
release-9-0-1.html	5.81 KB	-rw-r--r--
release-9-0-10.html	5.56 KB	-rw-r--r--
release-9-0-11.html	12.37 KB	-rw-r--r--
release-9-0-12.html	8.62 KB	-rw-r--r--
release-9-0-13.html	11.4 KB	-rw-r--r--
release-9-0-14.html	8.55 KB	-rw-r--r--
release-9-0-15.html	8.93 KB	-rw-r--r--
release-9-0-16.html	17 KB	-rw-r--r--
release-9-0-17.html	6.19 KB	-rw-r--r--
release-9-0-18.html	11.6 KB	-rw-r--r--
release-9-0-19.html	25.99 KB	-rw-r--r--
release-9-0-2.html	13.32 KB	-rw-r--r--
release-9-0-20.html	15.46 KB	-rw-r--r--
release-9-0-21.html	5.04 KB	-rw-r--r--
release-9-0-22.html	4.22 KB	-rw-r--r--
release-9-0-23.html	15.78 KB	-rw-r--r--
release-9-0-3.html	7.09 KB	-rw-r--r--
release-9-0-4.html	11.08 KB	-rw-r--r--
release-9-0-5.html	17.5 KB	-rw-r--r--
release-9-0-6.html	13.11 KB	-rw-r--r--
release-9-0-7.html	17.67 KB	-rw-r--r--
release-9-0-8.html	10.74 KB	-rw-r--r--
release-9-0-9.html	11.47 KB	-rw-r--r--
release-9-0.html	93.87 KB	-rw-r--r--
release-9-1-1.html	3.58 KB	-rw-r--r--
release-9-1-10.html	10.11 KB	-rw-r--r--
release-9-1-11.html	9.36 KB	-rw-r--r--
release-9-1-12.html	18.12 KB	-rw-r--r--
release-9-1-13.html	6.53 KB	-rw-r--r--
release-9-1-14.html	12.73 KB	-rw-r--r--
release-9-1-15.html	28.29 KB	-rw-r--r--
release-9-1-16.html	18.67 KB	-rw-r--r--
release-9-1-17.html	4.83 KB	-rw-r--r--
release-9-1-18.html	4.01 KB	-rw-r--r--
release-9-1-19.html	17.2 KB	-rw-r--r--
release-9-1-2.html	21.07 KB	-rw-r--r--
release-9-1-20.html	17.13 KB	-rw-r--r--
release-9-1-21.html	7.42 KB	-rw-r--r--
release-9-1-22.html	7.09 KB	-rw-r--r--
release-9-1-23.html	12.36 KB	-rw-r--r--
release-9-1-24.html	8.53 KB	-rw-r--r--
release-9-1-3.html	20.66 KB	-rw-r--r--
release-9-1-4.html	15.64 KB	-rw-r--r--
release-9-1-5.html	13.71 KB	-rw-r--r--
release-9-1-6.html	9.3 KB	-rw-r--r--
release-9-1-7.html	14.59 KB	-rw-r--r--
release-9-1-8.html	9.92 KB	-rw-r--r--
release-9-1-9.html	12.38 KB	-rw-r--r--
release-9-1.html	77.11 KB	-rw-r--r--
release-9-2-1.html	6.94 KB	-rw-r--r--
release-9-2-10.html	31.61 KB	-rw-r--r--
release-9-2-11.html	19.82 KB	-rw-r--r--
release-9-2-12.html	5.01 KB	-rw-r--r--
release-9-2-13.html	4.01 KB	-rw-r--r--
release-9-2-14.html	17.96 KB	-rw-r--r--
release-9-2-15.html	18.17 KB	-rw-r--r--
release-9-2-16.html	7.42 KB	-rw-r--r--
release-9-2-17.html	8 KB	-rw-r--r--
release-9-2-18.html	12.42 KB	-rw-r--r--
release-9-2-19.html	10.27 KB	-rw-r--r--
release-9-2-2.html	22.46 KB	-rw-r--r--
release-9-2-20.html	13.02 KB	-rw-r--r--
release-9-2-21.html	13.87 KB	-rw-r--r--
release-9-2-22.html	15.49 KB	-rw-r--r--
release-9-2-23.html	7.94 KB	-rw-r--r--
release-9-2-24.html	7.69 KB	-rw-r--r--
release-9-2-3.html	13.06 KB	-rw-r--r--
release-9-2-4.html	14.45 KB	-rw-r--r--
release-9-2-5.html	11.72 KB	-rw-r--r--
release-9-2-6.html	11.41 KB	-rw-r--r--
release-9-2-7.html	19.55 KB	-rw-r--r--
release-9-2-8.html	7.2 KB	-rw-r--r--
release-9-2-9.html	15.25 KB	-rw-r--r--
release-9-2.html	77.66 KB	-rw-r--r--
release.html	22.35 KB	-rw-r--r--
resources.html	4.13 KB	-rw-r--r--
role-attributes.html	7.67 KB	-rw-r--r--
role-membership.html	8.19 KB	-rw-r--r--
role-removal.html	5.18 KB	-rw-r--r--
routine-reindex.html	3.54 KB	-rw-r--r--
routine-vacuuming.html	37.13 KB	-rw-r--r--
row-estimation-examples.html	20.28 KB	-rw-r--r--
rowtypes.html	22.86 KB	-rw-r--r--
rule-system.html	4.02 KB	-rw-r--r--
rules-privileges.html	11.39 KB	-rw-r--r--
rules-status.html	4.41 KB	-rw-r--r--
rules-triggers.html	9.25 KB	-rw-r--r--
rules-update.html	31.85 KB	-rw-r--r--
rules-views.html	26.26 KB	-rw-r--r--
rules.html	4.83 KB	-rw-r--r--
runtime-config-autovacuum.html	10.72 KB	-rw-r--r--
runtime-config-client.html	32.05 KB	-rw-r--r--
runtime-config-compatible.html	14.48 KB	-rw-r--r--
runtime-config-connection.html	22.93 KB	-rw-r--r--
runtime-config-custom.html	3.46 KB	-rw-r--r--
runtime-config-developer.html	13.74 KB	-rw-r--r--
runtime-config-error-handling....	3.49 KB	-rw-r--r--
runtime-config-file-locations....	6.81 KB	-rw-r--r--
runtime-config-locks.html	7.46 KB	-rw-r--r--
runtime-config-logging.html	44.38 KB	-rw-r--r--
runtime-config-preset.html	8.51 KB	-rw-r--r--
runtime-config-query.html	24.37 KB	-rw-r--r--
runtime-config-replication.htm...	17.87 KB	-rw-r--r--
runtime-config-resource.html	27.25 KB	-rw-r--r--
runtime-config-short.html	6.53 KB	-rw-r--r--
runtime-config-statistics.html	8.41 KB	-rw-r--r--
runtime-config-wal.html	26.46 KB	-rw-r--r--
runtime-config.html	8.06 KB	-rw-r--r--
runtime.html	5.12 KB	-rw-r--r--
seg.html	15.11 KB	-rw-r--r--
sepgsql.html	30.11 KB	-rw-r--r--
server-programming.html	9.39 KB	-rw-r--r--
server-shutdown.html	6.32 KB	-rw-r--r--
server-start.html	13.88 KB	-rw-r--r--
source-format.html	5.01 KB	-rw-r--r--
source.html	3.98 KB	-rw-r--r--
sourcerepo.html	3.33 KB	-rw-r--r--
spgist-examples.html	2.64 KB	-rw-r--r--
spgist-extensibility.html	30.55 KB	-rw-r--r--
spgist-implementation.html	7.91 KB	-rw-r--r--
spgist-intro.html	4.22 KB	-rw-r--r--
spgist.html	2.9 KB	-rw-r--r--
spi-examples.html	6.07 KB	-rw-r--r--
spi-interface-support.html	3.68 KB	-rw-r--r--
spi-interface.html	5.86 KB	-rw-r--r--
spi-memory.html	6.92 KB	-rw-r--r--
spi-realloc.html	3.54 KB	-rw-r--r--
spi-spi-connect.html	3.96 KB	-rw-r--r--
spi-spi-copytuple.html	3.37 KB	-rw-r--r--
spi-spi-cursor-close.html	3.26 KB	-rw-r--r--
spi-spi-cursor-fetch.html	4.01 KB	-rw-r--r--
spi-spi-cursor-find.html	3.38 KB	-rw-r--r--
spi-spi-cursor-move.html	3.8 KB	-rw-r--r--
spi-spi-cursor-open-with-args....	6.03 KB	-rw-r--r--
spi-spi-cursor-open-with-param...	4.92 KB	-rw-r--r--
spi-spi-cursor-open.html	5.6 KB	-rw-r--r--
spi-spi-exec.html	3.51 KB	-rw-r--r--
spi-spi-execp.html	4.75 KB	-rw-r--r--
spi-spi-execute-plan-with-para...	4.78 KB	-rw-r--r--
spi-spi-execute-plan.html	5.76 KB	-rw-r--r--
spi-spi-execute-with-args.html	6.08 KB	-rw-r--r--
spi-spi-execute.html	12.3 KB	-rw-r--r--
spi-spi-finish.html	3.57 KB	-rw-r--r--
spi-spi-fname.html	3.68 KB	-rw-r--r--
spi-spi-fnumber.html	3.84 KB	-rw-r--r--
spi-spi-freeplan.html	3.42 KB	-rw-r--r--
spi-spi-freetuple.html	3.2 KB	-rw-r--r--
spi-spi-freetupletable.html	3.54 KB	-rw-r--r--
spi-spi-getargcount.html	3.61 KB	-rw-r--r--
spi-spi-getargtypeid.html	4.04 KB	-rw-r--r--
spi-spi-getbinval.html	4.19 KB	-rw-r--r--
spi-spi-getnspname.html	3.39 KB	-rw-r--r--
spi-spi-getrelname.html	3.27 KB	-rw-r--r--
spi-spi-gettype.html	3.63 KB	-rw-r--r--
spi-spi-gettypeid.html	3.63 KB	-rw-r--r--
spi-spi-getvalue.html	4.07 KB	-rw-r--r--
spi-spi-is-cursor-plan.html	4.45 KB	-rw-r--r--
spi-spi-keepplan.html	3.79 KB	-rw-r--r--
spi-spi-modifytuple.html	5.5 KB	-rw-r--r--
spi-spi-palloc.html	3.08 KB	-rw-r--r--
spi-spi-pfree.html	3.2 KB	-rw-r--r--
spi-spi-pop.html	2.68 KB	-rw-r--r--
spi-spi-prepare-cursor.html	4.94 KB	-rw-r--r--
spi-spi-prepare-params.html	4.31 KB	-rw-r--r--
spi-spi-prepare.html	7.48 KB	-rw-r--r--
spi-spi-push.html	3.65 KB	-rw-r--r--
spi-spi-returntuple.html	4 KB	-rw-r--r--
spi-spi-saveplan.html	4.47 KB	-rw-r--r--
spi-spi-scroll-cursor-fetch.ht...	4.7 KB	-rw-r--r--
spi-spi-scroll-cursor-move.htm...	4.78 KB	-rw-r--r--
spi-visibility.html	4.05 KB	-rw-r--r--
spi.html	10.59 KB	-rw-r--r--
sql-abort.html	4.08 KB	-rw-r--r--
sql-alteraggregate.html	5.97 KB	-rw-r--r--
sql-altercollation.html	4.96 KB	-rw-r--r--
sql-alterconversion.html	5.05 KB	-rw-r--r--
sql-alterdatabase.html	8.57 KB	-rw-r--r--
sql-alterdefaultprivileges.htm...	9.19 KB	-rw-r--r--
sql-alterdomain.html	10.85 KB	-rw-r--r--
sql-alterextension.html	11.47 KB	-rw-r--r--
sql-alterforeigndatawrapper.ht...	7.21 KB	-rw-r--r--
sql-alterforeigntable.html	12.41 KB	-rw-r--r--
sql-alterfunction.html	12.54 KB	-rw-r--r--
sql-altergroup.html	5.12 KB	-rw-r--r--
sql-alterindex.html	7.48 KB	-rw-r--r--
sql-alterlanguage.html	3.93 KB	-rw-r--r--
sql-alterlargeobject.html	3.64 KB	-rw-r--r--
sql-alteropclass.html	4.99 KB	-rw-r--r--
sql-alteroperator.html	5.31 KB	-rw-r--r--
sql-alteropfamily.html	13.25 KB	-rw-r--r--
sql-alterrole.html	12.72 KB	-rw-r--r--
sql-alterschema.html	4.21 KB	-rw-r--r--
sql-altersequence.html	12.73 KB	-rw-r--r--
sql-alterserver.html	5.79 KB	-rw-r--r--
sql-altertable.html	42.52 KB	-rw-r--r--
sql-altertablespace.html	5.73 KB	-rw-r--r--
sql-altertrigger.html	4.54 KB	-rw-r--r--
sql-altertsconfig.html	7.94 KB	-rw-r--r--
sql-altertsdictionary.html	6.39 KB	-rw-r--r--
sql-altertsparser.html	4.16 KB	-rw-r--r--
sql-altertstemplate.html	4.12 KB	-rw-r--r--
sql-altertype.html	10.93 KB	-rw-r--r--
sql-alteruser.html	4.61 KB	-rw-r--r--
sql-alterusermapping.html	5.58 KB	-rw-r--r--
sql-alterview.html	6.81 KB	-rw-r--r--
sql-analyze.html	10.42 KB	-rw-r--r--
sql-begin.html	6.54 KB	-rw-r--r--
sql-checkpoint.html	3.67 KB	-rw-r--r--
sql-close.html	4.87 KB	-rw-r--r--
sql-cluster.html	9.18 KB	-rw-r--r--
sql-commands.html	18.37 KB	-rw-r--r--
sql-comment.html	13.48 KB	-rw-r--r--
sql-commit-prepared.html	4.41 KB	-rw-r--r--
sql-commit.html	3.9 KB	-rw-r--r--
sql-copy.html	36.57 KB	-rw-r--r--
sql-createaggregate.html	13.5 KB	-rw-r--r--
sql-createcast.html	19.17 KB	-rw-r--r--
sql-createcollation.html	6.58 KB	-rw-r--r--
sql-createconversion.html	6.38 KB	-rw-r--r--
sql-createdatabase.html	11.85 KB	-rw-r--r--
sql-createdomain.html	8.34 KB	-rw-r--r--
sql-createextension.html	8.87 KB	-rw-r--r--
sql-createforeigndatawrapper.h...	7.87 KB	-rw-r--r--
sql-createforeigntable.html	7.54 KB	-rw-r--r--
sql-createfunction.html	30.35 KB	-rw-r--r--
sql-creategroup.html	3.92 KB	-rw-r--r--
sql-createindex.html	25.33 KB	-rw-r--r--
sql-createlanguage.html	14.54 KB	-rw-r--r--
sql-createopclass.html	12.38 KB	-rw-r--r--
sql-createoperator.html	10.44 KB	-rw-r--r--
sql-createopfamily.html	5.49 KB	-rw-r--r--
sql-createrole.html	18.87 KB	-rw-r--r--
sql-createrule.html	12.36 KB	-rw-r--r--
sql-createschema.html	8.12 KB	-rw-r--r--
sql-createsequence.html	13.54 KB	-rw-r--r--
sql-createserver.html	6.1 KB	-rw-r--r--
sql-createtable.html	57.79 KB	-rw-r--r--
sql-createtableas.html	12.47 KB	-rw-r--r--
sql-createtablespace.html	5.96 KB	-rw-r--r--
sql-createtrigger.html	22.63 KB	-rw-r--r--
sql-createtsconfig.html	5.23 KB	-rw-r--r--
sql-createtsdictionary.html	5.4 KB	-rw-r--r--
sql-createtsparser.html	5.81 KB	-rw-r--r--
sql-createtstemplate.html	5.31 KB	-rw-r--r--
sql-createtype.html	38.54 KB	-rw-r--r--
sql-createuser.html	4.42 KB	-rw-r--r--
sql-createusermapping.html	5.37 KB	-rw-r--r--
sql-createview.html	10.31 KB	-rw-r--r--
sql-deallocate.html	3.7 KB	-rw-r--r--
sql-declare.html	15.04 KB	-rw-r--r--
sql-delete.html	11.5 KB	-rw-r--r--
sql-discard.html	4.21 KB	-rw-r--r--
sql-do.html	5.08 KB	-rw-r--r--
sql-drop-owned.html	4.94 KB	-rw-r--r--
sql-dropaggregate.html	4.45 KB	-rw-r--r--
sql-dropcast.html	4.24 KB	-rw-r--r--
sql-dropcollation.html	4.31 KB	-rw-r--r--
sql-dropconversion.html	4.33 KB	-rw-r--r--
sql-dropdatabase.html	4.24 KB	-rw-r--r--
sql-dropdomain.html	4.16 KB	-rw-r--r--
sql-dropextension.html	4.67 KB	-rw-r--r--
sql-dropforeigndatawrapper.htm...	4.42 KB	-rw-r--r--
sql-dropforeigntable.html	4.45 KB	-rw-r--r--
sql-dropfunction.html	5.7 KB	-rw-r--r--
sql-dropgroup.html	2.98 KB	-rw-r--r--
sql-dropindex.html	5.06 KB	-rw-r--r--
sql-droplanguage.html	4.73 KB	-rw-r--r--
sql-dropopclass.html	5.54 KB	-rw-r--r--
sql-dropoperator.html	5.1 KB	-rw-r--r--
sql-dropopfamily.html	5.16 KB	-rw-r--r--
sql-droprole.html	5.04 KB	-rw-r--r--
sql-droprule.html	4.05 KB	-rw-r--r--
sql-dropschema.html	4.42 KB	-rw-r--r--
sql-dropsequence.html	4.26 KB	-rw-r--r--
sql-dropserver.html	4.17 KB	-rw-r--r--
sql-droptable.html	4.91 KB	-rw-r--r--
sql-droptablespace.html	4.48 KB	-rw-r--r--
sql-droptrigger.html	4.6 KB	-rw-r--r--
sql-droptsconfig.html	4.66 KB	-rw-r--r--
sql-droptsdictionary.html	4.58 KB	-rw-r--r--
sql-droptsparser.html	4.49 KB	-rw-r--r--
sql-droptstemplate.html	4.46 KB	-rw-r--r--
sql-droptype.html	4.36 KB	-rw-r--r--
sql-dropuser.html	3.11 KB	-rw-r--r--
sql-dropusermapping.html	4.57 KB	-rw-r--r--
sql-dropview.html	4.16 KB	-rw-r--r--
sql-end.html	4.06 KB	-rw-r--r--
sql-execute.html	4.95 KB	-rw-r--r--
sql-explain.html	16.69 KB	-rw-r--r--
sql-expressions.html	46.68 KB	-rw-r--r--
sql-fetch.html	13.92 KB	-rw-r--r--
sql-grant.html	28.56 KB	-rw-r--r--
sql-insert.html	12.56 KB	-rw-r--r--
sql-keywords-appendix.html	104.04 KB	-rw-r--r--
sql-listen.html	5.76 KB	-rw-r--r--
sql-load.html	4.11 KB	-rw-r--r--
sql-lock.html	11.59 KB	-rw-r--r--
sql-move.html	4.87 KB	-rw-r--r--
sql-notify.html	10.69 KB	-rw-r--r--
sql-prepare-transaction.html	8.44 KB	-rw-r--r--
sql-prepare.html	8.97 KB	-rw-r--r--
sql-reassign-owned.html	5.22 KB	-rw-r--r--
sql-reindex.html	10.84 KB	-rw-r--r--
sql-release-savepoint.html	4.89 KB	-rw-r--r--
sql-reset.html	4.88 KB	-rw-r--r--
sql-revoke.html	14.53 KB	-rw-r--r--
sql-rollback-prepared.html	4.52 KB	-rw-r--r--
sql-rollback-to.html	6.25 KB	-rw-r--r--
sql-rollback.html	3.9 KB	-rw-r--r--
sql-savepoint.html	5.47 KB	-rw-r--r--
sql-security-label.html	8.67 KB	-rw-r--r--
sql-select.html	77.68 KB	-rw-r--r--
sql-selectinto.html	7.46 KB	-rw-r--r--
sql-set-constraints.html	6.9 KB	-rw-r--r--
sql-set-role.html	6.75 KB	-rw-r--r--
sql-set-session-authorization....	5.92 KB	-rw-r--r--
sql-set-transaction.html	12.4 KB	-rw-r--r--
sql-set.html	11.77 KB	-rw-r--r--
sql-show.html	6.69 KB	-rw-r--r--
sql-start-transaction.html	4.87 KB	-rw-r--r--
sql-syntax-calling-funcs.html	7.89 KB	-rw-r--r--
sql-syntax-lexical.html	42.35 KB	-rw-r--r--
sql-syntax.html	5.3 KB	-rw-r--r--
sql-truncate.html	9.14 KB	-rw-r--r--
sql-unlisten.html	4.81 KB	-rw-r--r--
sql-update.html	15.3 KB	-rw-r--r--
sql-vacuum.html	10.42 KB	-rw-r--r--
sql-values.html	10.39 KB	-rw-r--r--
sql.html	13.25 KB	-rw-r--r--
ssh-tunnels.html	6.12 KB	-rw-r--r--
ssl-tcp.html	13.16 KB	-rw-r--r--
sslinfo.html	7.42 KB	-rw-r--r--
standby-settings.html	5.3 KB	-rw-r--r--
storage-file-layout.html	12.63 KB	-rw-r--r--
storage-fsm.html	3.73 KB	-rw-r--r--
storage-init.html	2.7 KB	-rw-r--r--
storage-page-layout.html	13.57 KB	-rw-r--r--
storage-toast.html	11.21 KB	-rw-r--r--
storage-vm.html	3.46 KB	-rw-r--r--
storage.html	2.88 KB	-rw-r--r--
stylesheet.css	1.5 KB	-rw-r--r--
supported-platforms.html	4.92 KB	-rw-r--r--
tablefunc.html	31.44 KB	-rw-r--r--
tcn.html	4.86 KB	-rw-r--r--
test-parser.html	4.42 KB	-rw-r--r--
textsearch-configuration.html	6.11 KB	-rw-r--r--
textsearch-controls.html	26.33 KB	-rw-r--r--
textsearch-debugging.html	16.82 KB	-rw-r--r--
textsearch-dictionaries.html	30.53 KB	-rw-r--r--
textsearch-features.html	20.81 KB	-rw-r--r--
textsearch-indexes.html	7.21 KB	-rw-r--r--
textsearch-intro.html	18.02 KB	-rw-r--r--
textsearch-limitations.html	3.77 KB	-rw-r--r--
textsearch-migration.html	4.92 KB	-rw-r--r--
textsearch-parsers.html	8.99 KB	-rw-r--r--
textsearch-psql.html	9.13 KB	-rw-r--r--
textsearch-tables.html	9.52 KB	-rw-r--r--
textsearch.html	5.74 KB	-rw-r--r--
transaction-iso.html	26.6 KB	-rw-r--r--
trigger-datachanges.html	4.95 KB	-rw-r--r--
trigger-definition.html	15.14 KB	-rw-r--r--
trigger-example.html	7.57 KB	-rw-r--r--
trigger-interface.html	10.47 KB	-rw-r--r--
triggers.html	3.71 KB	-rw-r--r--
tsearch2.html	9.72 KB	-rw-r--r--
tutorial-accessdb.html	6.88 KB	-rw-r--r--
tutorial-advanced-intro.html	3.26 KB	-rw-r--r--
tutorial-advanced.html	2.79 KB	-rw-r--r--
tutorial-agg.html	7.42 KB	-rw-r--r--
tutorial-arch.html	4.74 KB	-rw-r--r--
tutorial-concepts.html	3.75 KB	-rw-r--r--
tutorial-conclusion.html	2.78 KB	-rw-r--r--
tutorial-createdb.html	8.98 KB	-rw-r--r--
tutorial-delete.html	3.43 KB	-rw-r--r--
tutorial-fk.html	4.32 KB	-rw-r--r--
tutorial-inheritance.html	5.99 KB	-rw-r--r--
tutorial-install.html	4.42 KB	-rw-r--r--
tutorial-join.html	9.46 KB	-rw-r--r--
tutorial-populate.html	4.73 KB	-rw-r--r--
tutorial-select.html	7.84 KB	-rw-r--r--
tutorial-sql-intro.html	4.79 KB	-rw-r--r--
tutorial-sql.html	2.99 KB	-rw-r--r--
tutorial-start.html	2.57 KB	-rw-r--r--
tutorial-table.html	5.57 KB	-rw-r--r--
tutorial-transactions.html	9.71 KB	-rw-r--r--
tutorial-update.html	3.08 KB	-rw-r--r--
tutorial-views.html	3.3 KB	-rw-r--r--
tutorial-window.html	12.19 KB	-rw-r--r--
tutorial.html	5.09 KB	-rw-r--r--
typeconv-func.html	11.88 KB	-rw-r--r--
typeconv-oper.html	14.56 KB	-rw-r--r--
typeconv-overview.html	8.11 KB	-rw-r--r--
typeconv-query.html	5.32 KB	-rw-r--r--
typeconv-union-case.html	6.46 KB	-rw-r--r--
typeconv.html	3.63 KB	-rw-r--r--
unaccent.html	6.58 KB	-rw-r--r--
unsupported-features-sql-stand...	34.29 KB	-rw-r--r--
upgrading.html	12.5 KB	-rw-r--r--
user-manag.html	3.89 KB	-rw-r--r--
using-explain.html	40.84 KB	-rw-r--r--
uuid-ossp.html	7.06 KB	-rw-r--r--
vacuumlo.html	7.37 KB	-rw-r--r--
view-pg-available-extension-ve...	4.53 KB	-rw-r--r--
view-pg-available-extensions.h...	3.85 KB	-rw-r--r--
view-pg-cursors.html	5.54 KB	-rw-r--r--
view-pg-group.html	3.81 KB	-rw-r--r--
view-pg-indexes.html	4.06 KB	-rw-r--r--
view-pg-locks.html	14.11 KB	-rw-r--r--
view-pg-prepared-statements.ht...	4.94 KB	-rw-r--r--
view-pg-prepared-xacts.html	4.8 KB	-rw-r--r--
view-pg-roles.html	5.93 KB	-rw-r--r--
view-pg-rules.html	3.91 KB	-rw-r--r--
view-pg-seclabels.html	5 KB	-rw-r--r--
view-pg-settings.html	10.35 KB	-rw-r--r--
view-pg-shadow.html	5.25 KB	-rw-r--r--
view-pg-stats.html	8.68 KB	-rw-r--r--
view-pg-tables.html	4.72 KB	-rw-r--r--
view-pg-timezone-abbrevs.html	3.77 KB	-rw-r--r--
view-pg-timezone-names.html	4.08 KB	-rw-r--r--
view-pg-user-mappings.html	5.04 KB	-rw-r--r--
view-pg-user.html	4.41 KB	-rw-r--r--
view-pg-views.html	3.76 KB	-rw-r--r--
views-overview.html	6.39 KB	-rw-r--r--
wal-async-commit.html	8.8 KB	-rw-r--r--
wal-configuration.html	14.61 KB	-rw-r--r--
wal-internals.html	6.01 KB	-rw-r--r--
wal-intro.html	5.4 KB	-rw-r--r--
wal-reliability.html	11.21 KB	-rw-r--r--
wal.html	2.86 KB	-rw-r--r--
warm-standby-failover.html	5.96 KB	-rw-r--r--
warm-standby.html	33.83 KB	-rw-r--r--
xaggr.html	9.67 KB	-rw-r--r--
xfunc-c.html	76.68 KB	-rw-r--r--
xfunc-internal.html	3.91 KB	-rw-r--r--
xfunc-overload.html	5.77 KB	-rw-r--r--
xfunc-pl.html	2.92 KB	-rw-r--r--
xfunc-sql.html	37.14 KB	-rw-r--r--
xfunc-volatility.html	9.61 KB	-rw-r--r--
xfunc.html	4.41 KB	-rw-r--r--
xindex.html	43.55 KB	-rw-r--r--
xml2.html	16.5 KB	-rw-r--r--
xoper-optimization.html	22.6 KB	-rw-r--r--
xoper.html	4.72 KB	-rw-r--r--
xplang-install.html	10.87 KB	-rw-r--r--
xplang.html	4.14 KB	-rw-r--r--
xtypes.html	11.83 KB	-rw-r--r--

Code Editor : libpq-exec.html

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">
<HTML
><HEAD
><TITLE
>Command Execution Functions</TITLE
><META
NAME="GENERATOR"
CONTENT="Modular DocBook HTML Stylesheet Version 1.79"><LINK
REV="MADE"
HREF="mailto:pgsql-docs@postgresql.org"><LINK
REL="HOME"
TITLE="PostgreSQL 9.2.24 Documentation"
HREF="index.html"><LINK
REL="UP"
TITLE="libpq - C Library"
HREF="libpq.html"><LINK
REL="PREVIOUS"
TITLE="Connection Status Functions"
HREF="libpq-status.html"><LINK
REL="NEXT"
TITLE="Asynchronous Command Processing"
HREF="libpq-async.html"><LINK
REL="STYLESHEET"
TYPE="text/css"
HREF="stylesheet.css"><META
HTTP-EQUIV="Content-Type"
CONTENT="text/html; charset=ISO-8859-1"><META
NAME="creation"
CONTENT="2017-11-06T22:43:11"></HEAD
><BODY
CLASS="SECT1"
><DIV
CLASS="NAVHEADER"
><TABLE
SUMMARY="Header navigation table"
WIDTH="100%"
BORDER="0"
CELLPADDING="0"
CELLSPACING="0"
><TR
><TH
COLSPAN="5"
ALIGN="center"
VALIGN="bottom"
><A
HREF="index.html"
>PostgreSQL 9.2.24 Documentation</A
></TH
></TR
><TR
><TD
WIDTH="10%"
ALIGN="left"
VALIGN="top"
><A
TITLE="Connection Status Functions"
HREF="libpq-status.html"
ACCESSKEY="P"
>Prev</A
></TD
><TD
WIDTH="10%"
ALIGN="left"
VALIGN="top"
><A
HREF="libpq.html"
ACCESSKEY="U"
>Up</A
></TD
><TD
WIDTH="60%"
ALIGN="center"
VALIGN="bottom"
>Chapter 31. libpq - C Library</TD
><TD
WIDTH="20%"
ALIGN="right"
VALIGN="top"
><A
TITLE="Asynchronous Command Processing"
HREF="libpq-async.html"
ACCESSKEY="N"
>Next</A
></TD
></TR
></TABLE
><HR
ALIGN="LEFT"
WIDTH="100%"></DIV
><DIV
CLASS="SECT1"
><H1
CLASS="SECT1"
><A
NAME="LIBPQ-EXEC"
>31.3. Command Execution Functions</A
></H1
> Once a connection to a database server has been successfully
 established, the functions described here are used to perform
 SQL queries and commands.
 <DIV
CLASS="SECT2"
><H2
CLASS="SECT2"
><A
NAME="LIBPQ-EXEC-MAIN"
>31.3.1. Main Functions</A
></H2
> <DIV
CLASS="VARIABLELIST"
><DL
><DT
><A
NAME="LIBPQ-PQEXEC"
></A
><CODE
CLASS="FUNCTION"
>PQexec</CODE
>
 </DT
><DD
> Submits a command to the server and waits for the result.

<PRE
CLASS="SYNOPSIS"
>PGresult *PQexec(PGconn *conn, const char *command);</PRE
>
 Returns a <TT
CLASS="STRUCTNAME"
>PGresult</TT
> pointer or possibly a null
 pointer. A non-null pointer will generally be returned except in
 out-of-memory conditions or serious errors such as inability to send
 the command to the server. The <CODE
CLASS="FUNCTION"
>PQresultStatus</CODE
> function
 should be called to check the return value for any errors (including
 the value of a null pointer, in which case it will return
 <TT
CLASS="SYMBOL"
>PGRES_FATAL_ERROR</TT
>). Use
 <CODE
CLASS="FUNCTION"
>PQerrorMessage</CODE
> to get more information about such
 errors.
 </DD
></DL
></DIV
>

The command string can include multiple SQL commands
 (separated by semicolons). Multiple queries sent in a single
 <CODE
CLASS="FUNCTION"
>PQexec</CODE
> call are processed in a single transaction, unless
 there are explicit <TT
CLASS="COMMAND"
>BEGIN</TT
>/<TT
CLASS="COMMAND"
>COMMIT</TT
>
 commands included in the query string to divide it into multiple
 transactions. Note however that the returned
 <TT
CLASS="STRUCTNAME"
>PGresult</TT
> structure describes only the result
 of the last command executed from the string. Should one of the
 commands fail, processing of the string stops with it and the returned
 <TT
CLASS="STRUCTNAME"
>PGresult</TT
> describes the error condition.
 <DIV
CLASS="VARIABLELIST"
><DL
><DT
><A
NAME="LIBPQ-PQEXECPARAMS"
></A
><CODE
CLASS="FUNCTION"
>PQexecParams</CODE
>
 </DT
><DD
> Submits a command to the server and waits for the result,
 with the ability to pass parameters separately from the SQL
 command text.

<PRE
CLASS="SYNOPSIS"
>PGresult *PQexecParams(PGconn *conn,
 const char *command,
 int nParams,
 const Oid *paramTypes,
 const char * const *paramValues,
 const int *paramLengths,
 const int *paramFormats,
 int resultFormat);</PRE
>
 <CODE
CLASS="FUNCTION"
>PQexecParams</CODE
> is like <CODE
CLASS="FUNCTION"
>PQexec</CODE
>, but offers additional
 functionality: parameter values can be specified separately from the command
 string proper, and query results can be requested in either text or binary
 format. <CODE
CLASS="FUNCTION"
>PQexecParams</CODE
> is supported only in protocol 3.0 and later
 connections; it will fail when using protocol 2.0.
 The function arguments are:

<DIV
CLASS="VARIABLELIST"
><DL
><DT
><TT
CLASS="PARAMETER"
>conn</TT
></DT
><DD
> The connection object to send the command through.
 </DD
><DT
><TT
CLASS="PARAMETER"
>command</TT
></DT
><DD
> The SQL command string to be executed. If parameters are used,
 they are referred to in the command string as <TT
CLASS="LITERAL"
>$1</TT
>,
 <TT
CLASS="LITERAL"
>$2</TT
>, etc.
 </DD
><DT
><TT
CLASS="PARAMETER"
>nParams</TT
></DT
><DD
> The number of parameters supplied; it is the length of the arrays
 <TT
CLASS="PARAMETER"
>paramTypes[]</TT
>, <TT
CLASS="PARAMETER"
>paramValues[]</TT
>,
 <TT
CLASS="PARAMETER"
>paramLengths[]</TT
>, and <TT
CLASS="PARAMETER"
>paramFormats[]</TT
>. (The
 array pointers can be <TT
CLASS="SYMBOL"
>NULL</TT
> when <TT
CLASS="PARAMETER"
>nParams</TT
>
 is zero.)
 </DD
><DT
><TT
CLASS="PARAMETER"
>paramTypes[]</TT
></DT
><DD
> Specifies, by OID, the data types to be assigned to the
 parameter symbols. If <TT
CLASS="PARAMETER"
>paramTypes</TT
> is
 <TT
CLASS="SYMBOL"
>NULL</TT
>, or any particular element in the array
 is zero, the server infers a data type for the parameter symbol
 in the same way it would do for an untyped literal string.
 </DD
><DT
><TT
CLASS="PARAMETER"
>paramValues[]</TT
></DT
><DD
> Specifies the actual values of the parameters. A null pointer
 in this array means the corresponding parameter is null;
 otherwise the pointer points to a zero-terminated text string
 (for text format) or binary data in the format expected by the
 server (for binary format).
 </DD
><DT
><TT
CLASS="PARAMETER"
>paramLengths[]</TT
></DT
><DD
> Specifies the actual data lengths of binary-format parameters.
 It is ignored for null parameters and text-format parameters.
 The array pointer can be null when there are no binary parameters.
 </DD
><DT
><TT
CLASS="PARAMETER"
>paramFormats[]</TT
></DT
><DD
> Specifies whether parameters are text (put a zero in the
 array entry for the corresponding parameter) or binary (put
 a one in the array entry for the corresponding parameter).
 If the array pointer is null then all parameters are presumed
 to be text strings.
 Values passed in binary format require knowledge of
 the internal representation expected by the backend.
 For example, integers must be passed in network byte
 order. Passing <TT
CLASS="TYPE"
>numeric</TT
> values requires
 knowledge of the server storage format, as implemented
 in
 <TT
CLASS="FILENAME"
>src/backend/utils/adt/numeric.c::numeric_send()</TT
> and
 <TT
CLASS="FILENAME"
>src/backend/utils/adt/numeric.c::numeric_recv()</TT
>.
 </DD
><DT
><TT
CLASS="PARAMETER"
>resultFormat</TT
></DT
><DD
> Specify zero to obtain results in text format, or one to obtain
 results in binary format. (There is not currently a provision
 to obtain different result columns in different formats,
 although that is possible in the underlying protocol.)
 </DD
></DL
></DIV
>
 </DD
></DL
></DIV
>
 The primary advantage of <CODE
CLASS="FUNCTION"
>PQexecParams</CODE
> over
 <CODE
CLASS="FUNCTION"
>PQexec</CODE
> is that parameter values can be separated from the
 command string, thus avoiding the need for tedious and error-prone
 quoting and escaping.
 Unlike <CODE
CLASS="FUNCTION"
>PQexec</CODE
>, <CODE
CLASS="FUNCTION"
>PQexecParams</CODE
> allows at most
 one SQL command in the given string. (There can be semicolons in it,
 but not more than one nonempty command.) This is a limitation of the
 underlying protocol, but has some usefulness as an extra defense against
 SQL-injection attacks.
 <DIV
CLASS="TIP"
><BLOCKQUOTE
CLASS="TIP"
>Tip: Specifying parameter types via OIDs is tedious, particularly if you prefer
 not to hard-wire particular OID values into your program. However, you can
 avoid doing so even in cases where the server by itself cannot determine the
 type of the parameter, or chooses a different type than you want. In the
 SQL command text, attach an explicit cast to the parameter symbol to show what
 data type you will send. For example:
<PRE
CLASS="PROGRAMLISTING"
>SELECT * FROM mytable WHERE x = $1::bigint;</PRE
>
 This forces parameter <TT
CLASS="LITERAL"
>$1</TT
> to be treated as <TT
CLASS="TYPE"
>bigint</TT
>, whereas
 by default it would be assigned the same type as <TT
CLASS="LITERAL"
>x</TT
>. Forcing the
 parameter type decision, either this way or by specifying a numeric type OID,
 is strongly recommended when sending parameter values in binary format, because
 binary format has less redundancy than text format and so there is less chance
 that the server will detect a type mismatch mistake for you.
 </BLOCKQUOTE
></DIV
> <DIV
CLASS="VARIABLELIST"
><DL
><DT
><A
NAME="LIBPQ-PQPREPARE"
></A
><CODE
CLASS="FUNCTION"
>PQprepare</CODE
>
 </DT
><DD
> Submits a request to create a prepared statement with the
 given parameters, and waits for completion.
<PRE
CLASS="SYNOPSIS"
>PGresult *PQprepare(PGconn *conn,
 const char *stmtName,
 const char *query,
 int nParams,
 const Oid *paramTypes);</PRE
>
 <CODE
CLASS="FUNCTION"
>PQprepare</CODE
> creates a prepared statement for later
 execution with <CODE
CLASS="FUNCTION"
>PQexecPrepared</CODE
>. This feature allows
 commands that will be used repeatedly to be parsed and planned just
 once, rather than each time they are executed.
 <CODE
CLASS="FUNCTION"
>PQprepare</CODE
> is supported only in protocol 3.0 and later
 connections; it will fail when using protocol 2.0.
 The function creates a prepared statement named
 <TT
CLASS="PARAMETER"
>stmtName</TT
> from the <TT
CLASS="PARAMETER"
>query</TT
> string, which
 must contain a single SQL command. <TT
CLASS="PARAMETER"
>stmtName</TT
> can be
 <TT
CLASS="LITERAL"
>""</TT
> to create an unnamed statement, in which case any
 pre-existing unnamed statement is automatically replaced; otherwise
 it is an error if the statement name is already defined in the
 current session. If any parameters are used, they are referred
 to in the query as <TT
CLASS="LITERAL"
>$1</TT
>, <TT
CLASS="LITERAL"
>$2</TT
>, etc.
 <TT
CLASS="PARAMETER"
>nParams</TT
> is the number of parameters for which types
 are pre-specified in the array <TT
CLASS="PARAMETER"
>paramTypes[]</TT
>. (The
 array pointer can be <TT
CLASS="SYMBOL"
>NULL</TT
> when
 <TT
CLASS="PARAMETER"
>nParams</TT
> is zero.) <TT
CLASS="PARAMETER"
>paramTypes[]</TT
>
 specifies, by OID, the data types to be assigned to the parameter
 symbols. If <TT
CLASS="PARAMETER"
>paramTypes</TT
> is <TT
CLASS="SYMBOL"
>NULL</TT
>,
 or any particular element in the array is zero, the server assigns
 a data type to the parameter symbol in the same way it would do
 for an untyped literal string. Also, the query can use parameter
 symbols with numbers higher than <TT
CLASS="PARAMETER"
>nParams</TT
>; data types
 will be inferred for these symbols as well. (See
 <CODE
CLASS="FUNCTION"
>PQdescribePrepared</CODE
> for a means to find out
 what data types were inferred.)
 As with <CODE
CLASS="FUNCTION"
>PQexec</CODE
>, the result is normally a
 <TT
CLASS="STRUCTNAME"
>PGresult</TT
> object whose contents indicate
 server-side success or failure. A null result indicates
 out-of-memory or inability to send the command at all. Use
 <CODE
CLASS="FUNCTION"
>PQerrorMessage</CODE
> to get more information about
 such errors.
 </DD
></DL
></DIV
>

Prepared statements for use with <CODE
CLASS="FUNCTION"
>PQexecPrepared</CODE
> can also
 be created by executing SQL <A
HREF="sql-prepare.html"
>PREPARE</A
>
 statements. Also, although there is no libpq
 function for deleting a prepared statement, the SQL <A
HREF="sql-deallocate.html"
>DEALLOCATE</A
> statement
 can be used for that purpose.
 <DIV
CLASS="VARIABLELIST"
><DL
><DT
><A
NAME="LIBPQ-PQEXECPREPARED"
></A
><CODE
CLASS="FUNCTION"
>PQexecPrepared</CODE
>
 </DT
><DD
> Sends a request to execute a prepared statement with given
 parameters, and waits for the result.
<PRE
CLASS="SYNOPSIS"
>PGresult *PQexecPrepared(PGconn *conn,
 const char *stmtName,
 int nParams,
 const char * const *paramValues,
 const int *paramLengths,
 const int *paramFormats,
 int resultFormat);</PRE
>
 <CODE
CLASS="FUNCTION"
>PQexecPrepared</CODE
> is like <CODE
CLASS="FUNCTION"
>PQexecParams</CODE
>,
 but the command to be executed is specified by naming a
 previously-prepared statement, instead of giving a query string.
 This feature allows commands that will be used repeatedly to be
 parsed and planned just once, rather than each time they are
 executed. The statement must have been prepared previously in
 the current session. <CODE
CLASS="FUNCTION"
>PQexecPrepared</CODE
> is supported
 only in protocol 3.0 and later connections; it will fail when
 using protocol 2.0.
 The parameters are identical to <CODE
CLASS="FUNCTION"
>PQexecParams</CODE
>, except that the
 name of a prepared statement is given instead of a query string, and the
 <TT
CLASS="PARAMETER"
>paramTypes[]</TT
> parameter is not present (it is not needed since
 the prepared statement's parameter types were determined when it was created).
 </DD
><DT
><A
NAME="LIBPQ-PQDESCRIBEPREPARED"
></A
><CODE
CLASS="FUNCTION"
>PQdescribePrepared</CODE
>
 </DT
><DD
> Submits a request to obtain information about the specified
 prepared statement, and waits for completion.
<PRE
CLASS="SYNOPSIS"
>PGresult *PQdescribePrepared(PGconn *conn, const char *stmtName);</PRE
>
 <CODE
CLASS="FUNCTION"
>PQdescribePrepared</CODE
> allows an application to obtain
 information about a previously prepared statement.
 <CODE
CLASS="FUNCTION"
>PQdescribePrepared</CODE
> is supported only in protocol 3.0
 and later connections; it will fail when using protocol 2.0.
 <TT
CLASS="PARAMETER"
>stmtName</TT
> can be <TT
CLASS="LITERAL"
>""</TT
> or <TT
CLASS="SYMBOL"
>NULL</TT
> to reference
 the unnamed statement, otherwise it must be the name of an existing
 prepared statement. On success, a <TT
CLASS="STRUCTNAME"
>PGresult</TT
> with
 status <TT
CLASS="LITERAL"
>PGRES_COMMAND_OK</TT
> is returned. The
 functions <CODE
CLASS="FUNCTION"
>PQnparams</CODE
> and
 <CODE
CLASS="FUNCTION"
>PQparamtype</CODE
> can be applied to this
 <TT
CLASS="STRUCTNAME"
>PGresult</TT
> to obtain information about the parameters
 of the prepared statement, and the functions
 <CODE
CLASS="FUNCTION"
>PQnfields</CODE
>, <CODE
CLASS="FUNCTION"
>PQfname</CODE
>,
 <CODE
CLASS="FUNCTION"
>PQftype</CODE
>, etc provide information about the
 result columns (if any) of the statement.
 </DD
><DT
><A
NAME="LIBPQ-PQDESCRIBEPORTAL"
></A
><CODE
CLASS="FUNCTION"
>PQdescribePortal</CODE
>
 </DT
><DD
> Submits a request to obtain information about the specified
 portal, and waits for completion.
<PRE
CLASS="SYNOPSIS"
>PGresult *PQdescribePortal(PGconn *conn, const char *portalName);</PRE
>
 <CODE
CLASS="FUNCTION"
>PQdescribePortal</CODE
> allows an application to obtain
 information about a previously created portal.
 (libpq does not provide any direct access to
 portals, but you can use this function to inspect the properties
 of a cursor created with a <TT
CLASS="COMMAND"
>DECLARE CURSOR</TT
> SQL command.)
 <CODE
CLASS="FUNCTION"
>PQdescribePortal</CODE
> is supported only in protocol 3.0
 and later connections; it will fail when using protocol 2.0.
 <TT
CLASS="PARAMETER"
>portalName</TT
> can be <TT
CLASS="LITERAL"
>""</TT
> or <TT
CLASS="SYMBOL"
>NULL</TT
> to reference
 the unnamed portal, otherwise it must be the name of an existing
 portal. On success, a <TT
CLASS="STRUCTNAME"
>PGresult</TT
> with status
 <TT
CLASS="LITERAL"
>PGRES_COMMAND_OK</TT
> is returned. The functions
 <CODE
CLASS="FUNCTION"
>PQnfields</CODE
>, <CODE
CLASS="FUNCTION"
>PQfname</CODE
>,
 <CODE
CLASS="FUNCTION"
>PQftype</CODE
>, etc can be applied to the
 <TT
CLASS="STRUCTNAME"
>PGresult</TT
> to obtain information about the result
 columns (if any) of the portal.
 </DD
></DL
></DIV
>
 The <TT
CLASS="STRUCTNAME"
>PGresult</TT
>
 structure encapsulates the result returned by the server.
 libpq application programmers should be
 careful to maintain the <TT
CLASS="STRUCTNAME"
>PGresult</TT
> abstraction.
 Use the accessor functions below to get at the contents of
 <TT
CLASS="STRUCTNAME"
>PGresult</TT
>. Avoid directly referencing the
 fields of the <TT
CLASS="STRUCTNAME"
>PGresult</TT
> structure because they
 are subject to change in the future.

<DIV
CLASS="VARIABLELIST"
><DL
><DT
><A
NAME="LIBPQ-PQRESULTSTATUS"
></A
><CODE
CLASS="FUNCTION"
>PQresultStatus</CODE
>
 </DT
><DD
> Returns the result status of the command.
<PRE
CLASS="SYNOPSIS"
>ExecStatusType PQresultStatus(const PGresult *res);</PRE
>
 <CODE
CLASS="FUNCTION"
>PQresultStatus</CODE
> can return one of the following values:

<DIV
CLASS="VARIABLELIST"
><DL
><DT
><A
NAME="LIBPQ-PGRES-EMPTY-QUERY"
></A
><TT
CLASS="LITERAL"
>PGRES_EMPTY_QUERY</TT
></DT
><DD
> The string sent to the server was empty.
 </DD
><DT
><A
NAME="LIBPQ-PGRES-COMMAND-OK"
></A
><TT
CLASS="LITERAL"
>PGRES_COMMAND_OK</TT
></DT
><DD
> Successful completion of a command returning no data.
 </DD
><DT
><A
NAME="LIBPQ-PGRES-TUPLES-OK"
></A
><TT
CLASS="LITERAL"
>PGRES_TUPLES_OK</TT
></DT
><DD
> Successful completion of a command returning data (such as
 a <TT
CLASS="COMMAND"
>SELECT</TT
> or <TT
CLASS="COMMAND"
>SHOW</TT
>).
 </DD
><DT
><A
NAME="LIBPQ-PGRES-COPY-OUT"
></A
><TT
CLASS="LITERAL"
>PGRES_COPY_OUT</TT
></DT
><DD
> Copy Out (from server) data transfer started.
 </DD
><DT
><A
NAME="LIBPQ-PGRES-COPY-IN"
></A
><TT
CLASS="LITERAL"
>PGRES_COPY_IN</TT
></DT
><DD
> Copy In (to server) data transfer started.
 </DD
><DT
><A
NAME="LIBPQ-PGRES-BAD-RESPONSE"
></A
><TT
CLASS="LITERAL"
>PGRES_BAD_RESPONSE</TT
></DT
><DD
> The server's response was not understood.
 </DD
><DT
><A
NAME="LIBPQ-PGRES-NONFATAL-ERROR"
></A
><TT
CLASS="LITERAL"
>PGRES_NONFATAL_ERROR</TT
></DT
><DD
> A nonfatal error (a notice or warning) occurred.
 </DD
><DT
><A
NAME="LIBPQ-PGRES-FATAL-ERROR"
></A
><TT
CLASS="LITERAL"
>PGRES_FATAL_ERROR</TT
></DT
><DD
> A fatal error occurred.
 </DD
><DT
><A
NAME="LIBPQ-PGRES-COPY-BOTH"
></A
><TT
CLASS="LITERAL"
>PGRES_COPY_BOTH</TT
></DT
><DD
> Copy In/Out (to and from server) data transfer started. This
 feature is currently used only for streaming replication,
 so this status should not occur in ordinary applications.
 </DD
><DT
><A
NAME="LIBPQ-PGRES-SINGLE-TUPLE"
></A
><TT
CLASS="LITERAL"
>PGRES_SINGLE_TUPLE</TT
></DT
><DD
> The <TT
CLASS="STRUCTNAME"
>PGresult</TT
> contains a single result tuple
 from the current command. This status occurs only when
 single-row mode has been selected for the query
 (see <A
HREF="libpq-single-row-mode.html"
>Section 31.5</A
>).
 </DD
></DL
></DIV
>

If the result status is <TT
CLASS="LITERAL"
>PGRES_TUPLES_OK</TT
> or
 <TT
CLASS="LITERAL"
>PGRES_SINGLE_TUPLE</TT
>, then
 the functions described below can be used to retrieve the rows
 returned by the query. Note that a <TT
CLASS="COMMAND"
>SELECT</TT
>
 command that happens to retrieve zero rows still shows
 <TT
CLASS="LITERAL"
>PGRES_TUPLES_OK</TT
>.
 <TT
CLASS="LITERAL"
>PGRES_COMMAND_OK</TT
> is for commands that can never
 return rows (<TT
CLASS="COMMAND"
>INSERT</TT
>, <TT
CLASS="COMMAND"
>UPDATE</TT
>,
 etc.). A response of <TT
CLASS="LITERAL"
>PGRES_EMPTY_QUERY</TT
> might
 indicate a bug in the client software.
 A result of status <TT
CLASS="SYMBOL"
>PGRES_NONFATAL_ERROR</TT
> will
 never be returned directly by <CODE
CLASS="FUNCTION"
>PQexec</CODE
> or other
 query execution functions; results of this kind are instead passed
 to the notice processor (see <A
HREF="libpq-notice-processing.html"
>Section 31.12</A
>).
 </DD
><DT
><A
NAME="LIBPQ-PQRESSTATUS"
></A
><CODE
CLASS="FUNCTION"
>PQresStatus</CODE
>
 </DT
><DD
> Converts the enumerated type returned by
 <CODE
CLASS="FUNCTION"
>PQresultStatus</CODE
> into a string constant describing the
 status code. The caller should not free the result.

<PRE
CLASS="SYNOPSIS"
>char *PQresStatus(ExecStatusType status);</PRE
>
 </DD
><DT
><A
NAME="LIBPQ-PQRESULTERRORMESSAGE"
></A
><CODE
CLASS="FUNCTION"
>PQresultErrorMessage</CODE
>
 </DT
><DD
> Returns the error message associated with the command, or an empty string
 if there was no error.
<PRE
CLASS="SYNOPSIS"
>char *PQresultErrorMessage(const PGresult *res);</PRE
>
 If there was an error, the returned string will include a trailing
 newline. The caller should not free the result directly. It will
 be freed when the associated <TT
CLASS="STRUCTNAME"
>PGresult</TT
> handle is
 passed to <CODE
CLASS="FUNCTION"
>PQclear</CODE
>.
 Immediately following a <CODE
CLASS="FUNCTION"
>PQexec</CODE
> or
 <CODE
CLASS="FUNCTION"
>PQgetResult</CODE
> call,
 <CODE
CLASS="FUNCTION"
>PQerrorMessage</CODE
> (on the connection) will return
 the same string as <CODE
CLASS="FUNCTION"
>PQresultErrorMessage</CODE
> (on
 the result). However, a <TT
CLASS="STRUCTNAME"
>PGresult</TT
> will
 retain its error message until destroyed, whereas the connection's
 error message will change when subsequent operations are done.
 Use <CODE
CLASS="FUNCTION"
>PQresultErrorMessage</CODE
> when you want to
 know the status associated with a particular
 <TT
CLASS="STRUCTNAME"
>PGresult</TT
>; use
 <CODE
CLASS="FUNCTION"
>PQerrorMessage</CODE
> when you want to know the
 status from the latest operation on the connection.
 </DD
><DT
><A
NAME="LIBPQ-PQRESULTERRORFIELD"
></A
><CODE
CLASS="FUNCTION"
>PQresultErrorField</CODE
></DT
><DD
> Returns an individual field of an error report.
<PRE
CLASS="SYNOPSIS"
>char *PQresultErrorField(const PGresult *res, int fieldcode);</PRE
>
 <TT
CLASS="PARAMETER"
>fieldcode</TT
> is an error field identifier; see the symbols
 listed below. <TT
CLASS="SYMBOL"
>NULL</TT
> is returned if the
 <TT
CLASS="STRUCTNAME"
>PGresult</TT
> is not an error or warning result,
 or does not include the specified field. Field values will normally
 not include a trailing newline. The caller should not free the
 result directly. It will be freed when the
 associated <TT
CLASS="STRUCTNAME"
>PGresult</TT
> handle is passed to
 <CODE
CLASS="FUNCTION"
>PQclear</CODE
>.
 The following field codes are available:
 <DIV
CLASS="VARIABLELIST"
><DL
><DT
><A
NAME="LIBPQ-PG-DIAG-SEVERITY"
></A
><TT
CLASS="SYMBOL"
>PG_DIAG_SEVERITY</TT
></DT
><DD
> The severity; the field contents are <TT
CLASS="LITERAL"
>ERROR</TT
>,
 <TT
CLASS="LITERAL"
>FATAL</TT
>, or <TT
CLASS="LITERAL"
>PANIC</TT
> (in an error message),
 or <TT
CLASS="LITERAL"
>WARNING</TT
>, <TT
CLASS="LITERAL"
>NOTICE</TT
>, <TT
CLASS="LITERAL"
>DEBUG</TT
>,
 <TT
CLASS="LITERAL"
>INFO</TT
>, or <TT
CLASS="LITERAL"
>LOG</TT
> (in a notice message), or
 a localized translation of one of these. Always present.
 </DD
><DT
><A
NAME="LIBPQ-PG-DIAG-SQLSTATE"
></A
><TT
CLASS="SYMBOL"
>PG_DIAG_SQLSTATE</TT
></DT
><DD
> The SQLSTATE code for the error. The SQLSTATE code identifies
 the type of error that has occurred; it can be used by
 front-end applications to perform specific operations (such
 as error handling) in response to a particular database error.
 For a list of the possible SQLSTATE codes, see <A
HREF="errcodes-appendix.html"
>Appendix A</A
>. This field is not localizable,
 and is always present.
 </DD
><DT
><A
NAME="LIBPQ-PG-DIAG-MESSAGE-PRIMARY"
></A
><TT
CLASS="SYMBOL"
>PG_DIAG_MESSAGE_PRIMARY</TT
></DT
><DD
> The primary human-readable error message (typically one line).
 Always present.
 </DD
><DT
><A
NAME="LIBPQ-PG-DIAG-MESSAGE-DETAIL"
></A
><TT
CLASS="SYMBOL"
>PG_DIAG_MESSAGE_DETAIL</TT
></DT
><DD
> Detail: an optional secondary error message carrying more
 detail about the problem. Might run to multiple lines.
 </DD
><DT
><A
NAME="LIBPQ-PG-DIAG-MESSAGE-HINT"
></A
><TT
CLASS="SYMBOL"
>PG_DIAG_MESSAGE_HINT</TT
></DT
><DD
> Hint: an optional suggestion what to do about the problem.
 This is intended to differ from detail in that it offers advice
 (potentially inappropriate) rather than hard facts. Might
 run to multiple lines.
 </DD
><DT
><A
NAME="LIBPQ-PG-DIAG-STATEMENT-POSITION"
></A
><TT
CLASS="SYMBOL"
>PG_DIAG_STATEMENT_POSITION</TT
></DT
><DD
> A string containing a decimal integer indicating an error cursor
 position as an index into the original statement string. The
 first character has index 1, and positions are measured in
 characters not bytes.
 </DD
><DT
><A
NAME="LIBPQ-PG-DIAG-INTERNAL-POSITION"
></A
><TT
CLASS="SYMBOL"
>PG_DIAG_INTERNAL_POSITION</TT
></DT
><DD
> This is defined the same as the
 <TT
CLASS="SYMBOL"
>PG_DIAG_STATEMENT_POSITION</TT
> field, but it is used
 when the cursor position refers to an internally generated
 command rather than the one submitted by the client. The
 <TT
CLASS="SYMBOL"
>PG_DIAG_INTERNAL_QUERY</TT
> field will always appear when
 this field appears.
 </DD
><DT
><A
NAME="LIBPQ-PG-DIAG-INTERNAL-QUERY"
></A
><TT
CLASS="SYMBOL"
>PG_DIAG_INTERNAL_QUERY</TT
></DT
><DD
> The text of a failed internally-generated command. This could
 be, for example, a SQL query issued by a PL/pgSQL function.
 </DD
><DT
><A
NAME="LIBPQ-PG-DIAG-CONTEXT"
></A
><TT
CLASS="SYMBOL"
>PG_DIAG_CONTEXT</TT
></DT
><DD
> An indication of the context in which the error occurred.
 Presently this includes a call stack traceback of active
 procedural language functions and internally-generated queries.
 The trace is one entry per line, most recent first.
 </DD
><DT
><A
NAME="LIBPQ-PG-DIAG-SOURCE-FILE"
></A
><TT
CLASS="SYMBOL"
>PG_DIAG_SOURCE_FILE</TT
></DT
><DD
> The file name of the source-code location where the error was
 reported.
 </DD
><DT
><A
NAME="LIBPQ-PG-DIAG-SOURCE-LINE"
></A
><TT
CLASS="SYMBOL"
>PG_DIAG_SOURCE_LINE</TT
></DT
><DD
> The line number of the source-code location where the error
 was reported.
 </DD
><DT
><A
NAME="LIBPQ-PG-DIAG-SOURCE-FUNCTION"
></A
><TT
CLASS="SYMBOL"
>PG_DIAG_SOURCE_FUNCTION</TT
></DT
><DD
> The name of the source-code function reporting the error.
 </DD
></DL
></DIV
>
 The client is responsible for formatting displayed information to meet
 its needs; in particular it should break long lines as needed.
 Newline characters appearing in the error message fields should be
 treated as paragraph breaks, not line breaks.
 Errors generated internally by libpq will
 have severity and primary message, but typically no other fields.
 Errors returned by a pre-3.0-protocol server will include severity and
 primary message, and sometimes a detail message, but no other fields.
 Note that error fields are only available from
 <TT
CLASS="STRUCTNAME"
>PGresult</TT
> objects, not
 <TT
CLASS="STRUCTNAME"
>PGconn</TT
> objects; there is no
 <CODE
CLASS="FUNCTION"
>PQerrorField</CODE
> function.
 </DD
><DT
><A
NAME="LIBPQ-PQCLEAR"
></A
><CODE
CLASS="FUNCTION"
>PQclear</CODE
></DT
><DD
> Frees the storage associated with a
 <TT
CLASS="STRUCTNAME"
>PGresult</TT
>. Every command result should be
 freed via <CODE
CLASS="FUNCTION"
>PQclear</CODE
> when it is no longer
 needed.

<PRE
CLASS="SYNOPSIS"
>void PQclear(PGresult *res);</PRE
>
 You can keep a <TT
CLASS="STRUCTNAME"
>PGresult</TT
> object around for
 as long as you need it; it does not go away when you issue a new
 command, nor even if you close the connection. To get rid of it,
 you must call <CODE
CLASS="FUNCTION"
>PQclear</CODE
>. Failure to do this
 will result in memory leaks in your application.
 </DD
></DL
></DIV
>
 </DIV
><DIV
CLASS="SECT2"
><H2
CLASS="SECT2"
><A
NAME="LIBPQ-EXEC-SELECT-INFO"
>31.3.2. Retrieving Query Result Information</A
></H2
> These functions are used to extract information from a
 <TT
CLASS="STRUCTNAME"
>PGresult</TT
> object that represents a successful
 query result (that is, one that has status
 <TT
CLASS="LITERAL"
>PGRES_TUPLES_OK</TT
> or <TT
CLASS="LITERAL"
>PGRES_SINGLE_TUPLE</TT
>).
 They can also be used to extract
 information from a successful Describe operation: a Describe's result
 has all the same column information that actual execution of the query
 would provide, but it has zero rows. For objects with other status values,
 these functions will act as though the result has zero rows and zero columns.
 <DIV
CLASS="VARIABLELIST"
><DL
><DT
><A
NAME="LIBPQ-PQNTUPLES"
></A
><CODE
CLASS="FUNCTION"
>PQntuples</CODE
>
 </DT
><DD
> Returns the number of rows (tuples) in the query result.
 (Note that <TT
CLASS="STRUCTNAME"
>PGresult</TT
> objects are limited to no more
 than <TT
CLASS="LITERAL"
>INT_MAX</TT
> rows, so an <TT
CLASS="TYPE"
>int</TT
> result is
 sufficient.)

<PRE
CLASS="SYNOPSIS"
>int PQntuples(const PGresult *res);</PRE
>

</DD
><DT
><A
NAME="LIBPQ-PQNFIELDS"
></A
><CODE
CLASS="FUNCTION"
>PQnfields</CODE
>
 </DT
><DD
> Returns the number of columns (fields) in each row of the query
 result.

<PRE
CLASS="SYNOPSIS"
>int PQnfields(const PGresult *res);</PRE
>
 </DD
><DT
><A
NAME="LIBPQ-PQFNAME"
></A
><CODE
CLASS="FUNCTION"
>PQfname</CODE
>
 </DT
><DD
> Returns the column name associated with the given column number.
 Column numbers start at 0. The caller should not free the result
 directly. It will be freed when the associated
 <TT
CLASS="STRUCTNAME"
>PGresult</TT
> handle is passed to
 <CODE
CLASS="FUNCTION"
>PQclear</CODE
>.
<PRE
CLASS="SYNOPSIS"
>char *PQfname(const PGresult *res,
 int column_number);</PRE
>
 <TT
CLASS="SYMBOL"
>NULL</TT
> is returned if the column number is out of range.
 </DD
><DT
><A
NAME="LIBPQ-PQFNUMBER"
></A
><CODE
CLASS="FUNCTION"
>PQfnumber</CODE
>
 </DT
><DD
> Returns the column number associated with the given column name.
<PRE
CLASS="SYNOPSIS"
>int PQfnumber(const PGresult *res,
 const char *column_name);</PRE
>
 -1 is returned if the given name does not match any column.
 The given name is treated like an identifier in an SQL command,
 that is, it is downcased unless double-quoted. For example, given
 a query result generated from the SQL command:
<PRE
CLASS="PROGRAMLISTING"
>SELECT 1 AS FOO, 2 AS "BAR";</PRE
>
 we would have the results:
<PRE
CLASS="PROGRAMLISTING"
>PQfname(res, 0) foo
PQfname(res, 1) BAR
PQfnumber(res, "FOO") 0
PQfnumber(res, "foo") 0
PQfnumber(res, "BAR") -1
PQfnumber(res, "\"BAR\"") 1</PRE
>
 </DD
><DT
><A
NAME="LIBPQ-PQFTABLE"
></A
><CODE
CLASS="FUNCTION"
>PQftable</CODE
>
 </DT
><DD
> Returns the OID of the table from which the given column was
 fetched. Column numbers start at 0.
<PRE
CLASS="SYNOPSIS"
>Oid PQftable(const PGresult *res,
 int column_number);</PRE
>
 <TT
CLASS="LITERAL"
>InvalidOid</TT
> is returned if the column number is out of range,
 or if the specified column is not a simple reference to a table column,
 or when using pre-3.0 protocol.
 You can query the system table <TT
CLASS="LITERAL"
>pg_class</TT
> to determine
 exactly which table is referenced.
 The type <TT
CLASS="TYPE"
>Oid</TT
> and the constant
 <TT
CLASS="LITERAL"
>InvalidOid</TT
> will be defined when you include
 the libpq header file. They will both
 be some integer type.
 </DD
><DT
><A
NAME="LIBPQ-PQFTABLECOL"
></A
><CODE
CLASS="FUNCTION"
>PQftablecol</CODE
>
 </DT
><DD
> Returns the column number (within its table) of the column making
 up the specified query result column. Query-result column numbers
 start at 0, but table columns have nonzero numbers.
<PRE
CLASS="SYNOPSIS"
>int PQftablecol(const PGresult *res,
 int column_number);</PRE
>
 Zero is returned if the column number is out of range, or if the
 specified column is not a simple reference to a table column, or
 when using pre-3.0 protocol.
 </DD
><DT
><A
NAME="LIBPQ-PQFFORMAT"
></A
><CODE
CLASS="FUNCTION"
>PQfformat</CODE
>
 </DT
><DD
> Returns the format code indicating the format of the given
 column. Column numbers start at 0.
<PRE
CLASS="SYNOPSIS"
>int PQfformat(const PGresult *res,
 int column_number);</PRE
>
 Format code zero indicates textual data representation, while format
 code one indicates binary representation. (Other codes are reserved
 for future definition.)
 </DD
><DT
><A
NAME="LIBPQ-PQFTYPE"
></A
><CODE
CLASS="FUNCTION"
>PQftype</CODE
>
 </DT
><DD
> Returns the data type associated with the given column number.
 The integer returned is the internal OID number of the type.
 Column numbers start at 0.
<PRE
CLASS="SYNOPSIS"
>Oid PQftype(const PGresult *res,
 int column_number);</PRE
>
 You can query the system table <TT
CLASS="LITERAL"
>pg_type</TT
> to
 obtain the names and properties of the various data types. The
 <ACRONYM
CLASS="ACRONYM"
>OID</ACRONYM
>s of the built-in data types are defined
 in the file <TT
CLASS="FILENAME"
>src/include/catalog/pg_type.h</TT
>
 in the source tree.
 </DD
><DT
><A
NAME="LIBPQ-PQFMOD"
></A
><CODE
CLASS="FUNCTION"
>PQfmod</CODE
>
 </DT
><DD
> Returns the type modifier of the column associated with the
 given column number. Column numbers start at 0.
<PRE
CLASS="SYNOPSIS"
>int PQfmod(const PGresult *res,
 int column_number);</PRE
>
 The interpretation of modifier values is type-specific; they
 typically indicate precision or size limits. The value -1 is
 used to indicate "no information available". Most data
 types do not use modifiers, in which case the value is always
 -1.
 </DD
><DT
><A
NAME="LIBPQ-PQFSIZE"
></A
><CODE
CLASS="FUNCTION"
>PQfsize</CODE
>
 </DT
><DD
> Returns the size in bytes of the column associated with the
 given column number. Column numbers start at 0.
<PRE
CLASS="SYNOPSIS"
>int PQfsize(const PGresult *res,
 int column_number);</PRE
>
 <CODE
CLASS="FUNCTION"
>PQfsize</CODE
> returns the space allocated for this column
 in a database row, in other words the size of the server's
 internal representation of the data type. (Accordingly, it is
 not really very useful to clients.) A negative value indicates
 the data type is variable-length.
 </DD
><DT
><A
NAME="LIBPQ-PQBINARYTUPLES"
></A
><CODE
CLASS="FUNCTION"
>PQbinaryTuples</CODE
>
 </DT
><DD
> Returns 1 if the <TT
CLASS="STRUCTNAME"
>PGresult</TT
> contains binary data
 and 0 if it contains text data.
<PRE
CLASS="SYNOPSIS"
>int PQbinaryTuples(const PGresult *res);</PRE
>
 This function is deprecated (except for its use in connection with
 <TT
CLASS="COMMAND"
>COPY</TT
>), because it is possible for a single
 <TT
CLASS="STRUCTNAME"
>PGresult</TT
> to contain text data in some columns and
 binary data in others. <CODE
CLASS="FUNCTION"
>PQfformat</CODE
> is preferred.
 <CODE
CLASS="FUNCTION"
>PQbinaryTuples</CODE
> returns 1 only if all columns of the
 result are binary (format 1).
 </DD
><DT
><A
NAME="LIBPQ-PQGETVALUE"
></A
><CODE
CLASS="FUNCTION"
>PQgetvalue</CODE
>
 </DT
><DD
> Returns a single field value of one row of a
 <TT
CLASS="STRUCTNAME"
>PGresult</TT
>. Row and column numbers start
 at 0. The caller should not free the result directly. It will
 be freed when the associated <TT
CLASS="STRUCTNAME"
>PGresult</TT
> handle is
 passed to <CODE
CLASS="FUNCTION"
>PQclear</CODE
>.
<PRE
CLASS="SYNOPSIS"
>char *PQgetvalue(const PGresult *res,
 int row_number,
 int column_number);</PRE
>
 For data in text format, the value returned by
 <CODE
CLASS="FUNCTION"
>PQgetvalue</CODE
> is a null-terminated character
 string representation of the field value. For data in binary
 format, the value is in the binary representation determined by
 the data type's <CODE
CLASS="FUNCTION"
>typsend</CODE
> and <CODE
CLASS="FUNCTION"
>typreceive</CODE
>
 functions. (The value is actually followed by a zero byte in
 this case too, but that is not ordinarily useful, since the
 value is likely to contain embedded nulls.)
 An empty string is returned if the field value is null. See
 <CODE
CLASS="FUNCTION"
>PQgetisnull</CODE
> to distinguish null values from
 empty-string values.
 The pointer returned by <CODE
CLASS="FUNCTION"
>PQgetvalue</CODE
> points
 to storage that is part of the <TT
CLASS="STRUCTNAME"
>PGresult</TT
>
 structure. One should not modify the data it points to, and one
 must explicitly copy the data into other storage if it is to be
 used past the lifetime of the <TT
CLASS="STRUCTNAME"
>PGresult</TT
>
 structure itself.
 </DD
><DT
><A
NAME="LIBPQ-PQGETISNULL"
></A
><CODE
CLASS="FUNCTION"
>PQgetisnull</CODE
>
 
 </DT
><DD
> Tests a field for a null value. Row and column numbers start
 at 0.
<PRE
CLASS="SYNOPSIS"
>int PQgetisnull(const PGresult *res,
 int row_number,
 int column_number);</PRE
>
 This function returns 1 if the field is null and 0 if it
 contains a non-null value. (Note that
 <CODE
CLASS="FUNCTION"
>PQgetvalue</CODE
> will return an empty string,
 not a null pointer, for a null field.)
 </DD
><DT
><A
NAME="LIBPQ-PQGETLENGTH"
></A
><CODE
CLASS="FUNCTION"
>PQgetlength</CODE
>
 </DT
><DD
> Returns the actual length of a field value in bytes. Row and
 column numbers start at 0.
<PRE
CLASS="SYNOPSIS"
>int PQgetlength(const PGresult *res,
 int row_number,
 int column_number);</PRE
>
 This is the actual data length for the particular data value,
 that is, the size of the object pointed to by
 <CODE
CLASS="FUNCTION"
>PQgetvalue</CODE
>. For text data format this is
 the same as <CODE
CLASS="FUNCTION"
>strlen()</CODE
>. For binary format this is
 essential information. Note that one should not
 rely on <CODE
CLASS="FUNCTION"
>PQfsize</CODE
> to obtain the actual data
 length.
 </DD
><DT
><A
NAME="LIBPQ-PQNPARAMS"
></A
><CODE
CLASS="FUNCTION"
>PQnparams</CODE
>
 </DT
><DD
> Returns the number of parameters of a prepared statement.
<PRE
CLASS="SYNOPSIS"
>int PQnparams(const PGresult *res);</PRE
>
 This function is only useful when inspecting the result of
 <CODE
CLASS="FUNCTION"
>PQdescribePrepared</CODE
>. For other types of queries it
 will return zero.
 </DD
><DT
><A
NAME="LIBPQ-PQPARAMTYPE"
></A
><CODE
CLASS="FUNCTION"
>PQparamtype</CODE
>
 </DT
><DD
> Returns the data type of the indicated statement parameter.
 Parameter numbers start at 0.
<PRE
CLASS="SYNOPSIS"
>Oid PQparamtype(const PGresult *res, int param_number);</PRE
>
 This function is only useful when inspecting the result of
 <CODE
CLASS="FUNCTION"
>PQdescribePrepared</CODE
>. For other types of queries it
 will return zero.
 </DD
><DT
><A
NAME="LIBPQ-PQPRINT"
></A
><CODE
CLASS="FUNCTION"
>PQprint</CODE
>
 </DT
><DD
> Prints out all the rows and, optionally, the column names to
 the specified output stream.
<PRE
CLASS="SYNOPSIS"
>void PQprint(FILE *fout, /* output stream */
 const PGresult *res,
 const PQprintOpt *po);
typedef struct
{
 pqbool header; /* print output field headings and row count */
 pqbool align; /* fill align the fields */
 pqbool standard; /* old brain dead format */
 pqbool html3; /* output HTML tables */
 pqbool expanded; /* expand tables */
 pqbool pager; /* use pager for output if needed */
 char *fieldSep; /* field separator */
 char *tableOpt; /* attributes for HTML table element */
 char *caption; /* HTML table caption */
 char **fieldName; /* null-terminated array of replacement field names */
} PQprintOpt;</PRE
>
 This function was formerly used by psql
 to print query results, but this is no longer the case. Note
 that it assumes all the data is in text format.
 </DD
></DL
></DIV
></DIV
><DIV
CLASS="SECT2"
><H2
CLASS="SECT2"
><A
NAME="LIBPQ-EXEC-NONSELECT"
>31.3.3. Retrieving Other Result Information</A
></H2
> These functions are used to extract other information from
 <TT
CLASS="STRUCTNAME"
>PGresult</TT
> objects.
 <DIV
CLASS="VARIABLELIST"
><DL
><DT
><A
NAME="LIBPQ-PQCMDSTATUS"
></A
><CODE
CLASS="FUNCTION"
>PQcmdStatus</CODE
>
 </DT
><DD
> Returns the command status tag from the SQL command that generated
 the <TT
CLASS="STRUCTNAME"
>PGresult</TT
>.
<PRE
CLASS="SYNOPSIS"
>char *PQcmdStatus(PGresult *res);</PRE
>
 Commonly this is just the name of the command, but it might include
 additional data such as the number of rows processed. The caller
 should not free the result directly. It will be freed when the
 associated <TT
CLASS="STRUCTNAME"
>PGresult</TT
> handle is passed to
 <CODE
CLASS="FUNCTION"
>PQclear</CODE
>.
 </DD
><DT
><A
NAME="LIBPQ-PQCMDTUPLES"
></A
><CODE
CLASS="FUNCTION"
>PQcmdTuples</CODE
>
 </DT
><DD
> Returns the number of rows affected by the SQL command.
<PRE
CLASS="SYNOPSIS"
>char *PQcmdTuples(PGresult *res);</PRE
>
 This function returns a string containing the number of rows
 affected by the <ACRONYM
CLASS="ACRONYM"
>SQL</ACRONYM
> statement that generated the
 <TT
CLASS="STRUCTNAME"
>PGresult</TT
>. This function can only be used following
 the execution of a <TT
CLASS="COMMAND"
>SELECT</TT
>, <TT
CLASS="COMMAND"
>CREATE TABLE AS</TT
>,
 <TT
CLASS="COMMAND"
>INSERT</TT
>, <TT
CLASS="COMMAND"
>UPDATE</TT
>, <TT
CLASS="COMMAND"
>DELETE</TT
>,
 <TT
CLASS="COMMAND"
>MOVE</TT
>, <TT
CLASS="COMMAND"
>FETCH</TT
>, or <TT
CLASS="COMMAND"
>COPY</TT
> statement,
 or an <TT
CLASS="COMMAND"
>EXECUTE</TT
> of a prepared query that contains an
 <TT
CLASS="COMMAND"
>INSERT</TT
>, <TT
CLASS="COMMAND"
>UPDATE</TT
>, or <TT
CLASS="COMMAND"
>DELETE</TT
> statement.
 If the command that generated the <TT
CLASS="STRUCTNAME"
>PGresult</TT
> was anything
 else, <CODE
CLASS="FUNCTION"
>PQcmdTuples</CODE
> returns an empty string. The caller
 should not free the return value directly. It will be freed when
 the associated <TT
CLASS="STRUCTNAME"
>PGresult</TT
> handle is passed to
 <CODE
CLASS="FUNCTION"
>PQclear</CODE
>.
 </DD
><DT
><A
NAME="LIBPQ-PQOIDVALUE"
></A
><CODE
CLASS="FUNCTION"
>PQoidValue</CODE
>
 </DT
><DD
> Returns the OID
 of the inserted row, if the <ACRONYM
CLASS="ACRONYM"
>SQL</ACRONYM
> command was an
 <TT
CLASS="COMMAND"
>INSERT</TT
> that inserted exactly one row into a table that
 has OIDs, or a <TT
CLASS="COMMAND"
>EXECUTE</TT
> of a prepared query containing
 a suitable <TT
CLASS="COMMAND"
>INSERT</TT
> statement. Otherwise, this function
 returns <TT
CLASS="LITERAL"
>InvalidOid</TT
>. This function will also
 return <TT
CLASS="LITERAL"
>InvalidOid</TT
> if the table affected by the
 <TT
CLASS="COMMAND"
>INSERT</TT
> statement does not contain OIDs.
<PRE
CLASS="SYNOPSIS"
>Oid PQoidValue(const PGresult *res);</PRE
>
 </DD
><DT
><A
NAME="LIBPQ-PQOIDSTATUS"
></A
><CODE
CLASS="FUNCTION"
>PQoidStatus</CODE
>
 </DT
><DD
> This function is deprecated in favor of
 <CODE
CLASS="FUNCTION"
>PQoidValue</CODE
> and is not thread-safe.
 It returns a string with the OID of the inserted row, while
 <CODE
CLASS="FUNCTION"
>PQoidValue</CODE
> returns the OID value.
<PRE
CLASS="SYNOPSIS"
>char *PQoidStatus(const PGresult *res);</PRE
>
 </DD
></DL
></DIV
></DIV
><DIV
CLASS="SECT2"
><H2
CLASS="SECT2"
><A
NAME="LIBPQ-EXEC-ESCAPE-STRING"
>31.3.4. Escaping Strings for Inclusion in SQL Commands</A
></H2
><DIV
CLASS="VARIABLELIST"
><DL
><DT
><A
NAME="LIBPQ-PQESCAPELITERAL"
></A
><CODE
CLASS="FUNCTION"
>PQescapeLiteral</CODE
>
 </DT
><DD
><PRE
CLASS="SYNOPSIS"
>char *PQescapeLiteral(PGconn *conn, const char *str, size_t length);</PRE
>
 <CODE
CLASS="FUNCTION"
>PQescapeLiteral</CODE
> escapes a string for
 use within an SQL command. This is useful when inserting data
 values as literal constants in SQL commands. Certain characters
 (such as quotes and backslashes) must be escaped to prevent them
 from being interpreted specially by the SQL parser.
 <CODE
CLASS="FUNCTION"
>PQescapeLiteral</CODE
> performs this operation.
 <CODE
CLASS="FUNCTION"
>PQescapeLiteral</CODE
> returns an escaped version of the
 <TT
CLASS="PARAMETER"
>str</TT
> parameter in memory allocated with
 <CODE
CLASS="FUNCTION"
>malloc()</CODE
>. This memory should be freed using
 <CODE
CLASS="FUNCTION"
>PQfreemem()</CODE
> when the result is no longer needed.
 A terminating zero byte is not required, and should not be
 counted in <TT
CLASS="PARAMETER"
>length</TT
>. (If a terminating zero byte is found
 before <TT
CLASS="PARAMETER"
>length</TT
> bytes are processed,
 <CODE
CLASS="FUNCTION"
>PQescapeLiteral</CODE
> stops at the zero; the behavior is
 thus rather like <CODE
CLASS="FUNCTION"
>strncpy</CODE
>.) The
 return string has all special characters replaced so that they can
 be properly processed by the PostgreSQL
 string literal parser. A terminating zero byte is also added. The
 single quotes that must surround PostgreSQL
 string literals are included in the result string.
 On error, <CODE
CLASS="FUNCTION"
>PQescapeLiteral</CODE
> returns <TT
CLASS="SYMBOL"
>NULL</TT
> and a suitable
 message is stored in the <TT
CLASS="PARAMETER"
>conn</TT
> object.
 <DIV
CLASS="TIP"
><BLOCKQUOTE
CLASS="TIP"
>Tip: It is especially important to do proper escaping when handling
 strings that were received from an untrustworthy source.
 Otherwise there is a security risk: you are vulnerable to
 "SQL injection" attacks wherein unwanted SQL commands are
 fed to your database.
 </BLOCKQUOTE
></DIV
> Note that it is not necessary nor correct to do escaping when a data
 value is passed as a separate parameter in <CODE
CLASS="FUNCTION"
>PQexecParams</CODE
> or
 its sibling routines.
 </DD
><DT
><A
NAME="LIBPQ-PQESCAPEIDENTIFIER"
></A
><CODE
CLASS="FUNCTION"
>PQescapeIdentifier</CODE
>
 </DT
><DD
><PRE
CLASS="SYNOPSIS"
>char *PQescapeIdentifier(PGconn *conn, const char *str, size_t length);</PRE
>
 <CODE
CLASS="FUNCTION"
>PQescapeIdentifier</CODE
> escapes a string for
 use as an SQL identifier, such as a table, column, or function name.
 This is useful when a user-supplied identifier might contain
 special characters that would otherwise not be interpreted as part
 of the identifier by the SQL parser, or when the identifier might
 contain upper case characters whose case should be preserved.
 <CODE
CLASS="FUNCTION"
>PQescapeIdentifier</CODE
> returns a version of the
 <TT
CLASS="PARAMETER"
>str</TT
> parameter escaped as an SQL identifier
 in memory allocated with <CODE
CLASS="FUNCTION"
>malloc()</CODE
>. This memory must be
 freed using <CODE
CLASS="FUNCTION"
>PQfreemem()</CODE
> when the result is no longer
 needed. A terminating zero byte is not required, and should not be
 counted in <TT
CLASS="PARAMETER"
>length</TT
>. (If a terminating zero byte is found
 before <TT
CLASS="PARAMETER"
>length</TT
> bytes are processed,
 <CODE
CLASS="FUNCTION"
>PQescapeIdentifier</CODE
> stops at the zero; the behavior is
 thus rather like <CODE
CLASS="FUNCTION"
>strncpy</CODE
>.) The
 return string has all special characters replaced so that it
 will be properly processed as an SQL identifier. A terminating zero byte
 is also added. The return string will also be surrounded by double
 quotes.
 On error, <CODE
CLASS="FUNCTION"
>PQescapeIdentifier</CODE
> returns <TT
CLASS="SYMBOL"
>NULL</TT
> and a suitable
 message is stored in the <TT
CLASS="PARAMETER"
>conn</TT
> object.
 <DIV
CLASS="TIP"
><BLOCKQUOTE
CLASS="TIP"
>Tip: As with string literals, to prevent SQL injection attacks,
 SQL identifiers must be escaped when they are received from an
 untrustworthy source.
 </BLOCKQUOTE
></DIV
></DD
><DT
><A
NAME="LIBPQ-PQESCAPESTRINGCONN"
></A
><CODE
CLASS="FUNCTION"
>PQescapeStringConn</CODE
>
 </DT
><DD
><PRE
CLASS="SYNOPSIS"
>size_t PQescapeStringConn(PGconn *conn,
 char *to, const char *from, size_t length,
 int *error);</PRE
>
 <CODE
CLASS="FUNCTION"
>PQescapeStringConn</CODE
> escapes string literals, much like
 <CODE
CLASS="FUNCTION"
>PQescapeLiteral</CODE
>. Unlike <CODE
CLASS="FUNCTION"
>PQescapeLiteral</CODE
>,
 the caller is responsible for providing an appropriately sized buffer.
 Furthermore, <CODE
CLASS="FUNCTION"
>PQescapeStringConn</CODE
> does not generate the
 single quotes that must surround PostgreSQL string
 literals; they should be provided in the SQL command that the
 result is inserted into. The parameter <TT
CLASS="PARAMETER"
>from</TT
> points to
 the first character of the string that is to be escaped, and the
 <TT
CLASS="PARAMETER"
>length</TT
> parameter gives the number of bytes in this
 string. A terminating zero byte is not required, and should not be
 counted in <TT
CLASS="PARAMETER"
>length</TT
>. (If a terminating zero byte is found
 before <TT
CLASS="PARAMETER"
>length</TT
> bytes are processed,
 <CODE
CLASS="FUNCTION"
>PQescapeStringConn</CODE
> stops at the zero; the behavior is
 thus rather like <CODE
CLASS="FUNCTION"
>strncpy</CODE
>.) <TT
CLASS="PARAMETER"
>to</TT
> shall point
 to a buffer that is able to hold at least one more byte than twice
 the value of <TT
CLASS="PARAMETER"
>length</TT
>, otherwise the behavior is undefined.
 Behavior is likewise undefined if the <TT
CLASS="PARAMETER"
>to</TT
> and
 <TT
CLASS="PARAMETER"
>from</TT
> strings overlap.
 If the <TT
CLASS="PARAMETER"
>error</TT
> parameter is not <TT
CLASS="SYMBOL"
>NULL</TT
>, then
 <TT
CLASS="LITERAL"
>*error</TT
> is set to zero on success, nonzero on error.
 Presently the only possible error conditions involve invalid multibyte
 encoding in the source string. The output string is still generated
 on error, but it can be expected that the server will reject it as
 malformed. On error, a suitable message is stored in the
 <TT
CLASS="PARAMETER"
>conn</TT
> object, whether or not <TT
CLASS="PARAMETER"
>error</TT
> is <TT
CLASS="SYMBOL"
>NULL</TT
>.
 <CODE
CLASS="FUNCTION"
>PQescapeStringConn</CODE
> returns the number of bytes written
 to <TT
CLASS="PARAMETER"
>to</TT
>, not including the terminating zero byte.
 </DD
><DT
><A
NAME="LIBPQ-PQESCAPESTRING"
></A
><CODE
CLASS="FUNCTION"
>PQescapeString</CODE
>
 </DT
><DD
> <CODE
CLASS="FUNCTION"
>PQescapeString</CODE
> is an older, deprecated version of
 <CODE
CLASS="FUNCTION"
>PQescapeStringConn</CODE
>.
<PRE
CLASS="SYNOPSIS"
>size_t PQescapeString (char *to, const char *from, size_t length);</PRE
>
 The only difference from <CODE
CLASS="FUNCTION"
>PQescapeStringConn</CODE
> is that
 <CODE
CLASS="FUNCTION"
>PQescapeString</CODE
> does not take <TT
CLASS="STRUCTNAME"
>PGconn</TT
>
 or <TT
CLASS="PARAMETER"
>error</TT
> parameters.
 Because of this, it cannot adjust its behavior depending on the
 connection properties (such as character encoding) and therefore
 it might give the wrong results. Also, it has no way
 to report error conditions.
 <CODE
CLASS="FUNCTION"
>PQescapeString</CODE
> can be used safely in
 client programs that work with only one PostgreSQL
 connection at a time (in this case it can find out what it needs to
 know "behind the scenes"). In other contexts it is a security
 hazard and should be avoided in favor of
 <CODE
CLASS="FUNCTION"
>PQescapeStringConn</CODE
>.
 </DD
><DT
><A
NAME="LIBPQ-PQESCAPEBYTEACONN"
></A
><CODE
CLASS="FUNCTION"
>PQescapeByteaConn</CODE
>
 </DT
><DD
> Escapes binary data for use within an SQL command with the type
 <TT
CLASS="TYPE"
>bytea</TT
>. As with <CODE
CLASS="FUNCTION"
>PQescapeStringConn</CODE
>,
 this is only used when inserting data directly into an SQL command string.
<PRE
CLASS="SYNOPSIS"
>unsigned char *PQescapeByteaConn(PGconn *conn,
 const unsigned char *from,
 size_t from_length,
 size_t *to_length);</PRE
>
 Certain byte values must be escaped when used as part of a
 <TT
CLASS="TYPE"
>bytea</TT
> literal in an <ACRONYM
CLASS="ACRONYM"
>SQL</ACRONYM
> statement.
 <CODE
CLASS="FUNCTION"
>PQescapeByteaConn</CODE
> escapes bytes using
 either hex encoding or backslash escaping. See <A
HREF="datatype-binary.html"
>Section 8.4</A
> for more information.
 The <TT
CLASS="PARAMETER"
>from</TT
> parameter points to the first
 byte of the string that is to be escaped, and the
 <TT
CLASS="PARAMETER"
>from_length</TT
> parameter gives the number of
 bytes in this binary string. (A terminating zero byte is
 neither necessary nor counted.) The <TT
CLASS="PARAMETER"
>to_length</TT
>
 parameter points to a variable that will hold the resultant
 escaped string length. This result string length includes the terminating
 zero byte of the result.
 <CODE
CLASS="FUNCTION"
>PQescapeByteaConn</CODE
> returns an escaped version of the
 <TT
CLASS="PARAMETER"
>from</TT
> parameter binary string in memory
 allocated with <CODE
CLASS="FUNCTION"
>malloc()</CODE
>. This memory should be freed using
 <CODE
CLASS="FUNCTION"
>PQfreemem()</CODE
> when the result is no longer needed. The
 return string has all special characters replaced so that they can
 be properly processed by the PostgreSQL
 string literal parser, and the <TT
CLASS="TYPE"
>bytea</TT
> input function. A
 terminating zero byte is also added. The single quotes that must
 surround PostgreSQL string literals are
 not part of the result string.
 On error, a null pointer is returned, and a suitable error message
 is stored in the <TT
CLASS="PARAMETER"
>conn</TT
> object. Currently, the only
 possible error is insufficient memory for the result string.
 </DD
><DT
><A
NAME="LIBPQ-PQESCAPEBYTEA"
></A
><CODE
CLASS="FUNCTION"
>PQescapeBytea</CODE
>
 </DT
><DD
> <CODE
CLASS="FUNCTION"
>PQescapeBytea</CODE
> is an older, deprecated version of
 <CODE
CLASS="FUNCTION"
>PQescapeByteaConn</CODE
>.
<PRE
CLASS="SYNOPSIS"
>unsigned char *PQescapeBytea(const unsigned char *from,
 size_t from_length,
 size_t *to_length);</PRE
>
 The only difference from <CODE
CLASS="FUNCTION"
>PQescapeByteaConn</CODE
> is that
 <CODE
CLASS="FUNCTION"
>PQescapeBytea</CODE
> does not take a <TT
CLASS="STRUCTNAME"
>PGconn</TT
>
 parameter. Because of this, <CODE
CLASS="FUNCTION"
>PQescapeBytea</CODE
> can
 only be used safely in client programs that use a single
 PostgreSQL connection at a time (in this case
 it can find out what it needs to know "behind the
 scenes"). It might give the wrong results if
 used in programs that use multiple database connections (use
 <CODE
CLASS="FUNCTION"
>PQescapeByteaConn</CODE
> in such cases).
 </DD
><DT
><A
NAME="LIBPQ-PQUNESCAPEBYTEA"
></A
><CODE
CLASS="FUNCTION"
>PQunescapeBytea</CODE
>
 </DT
><DD
> Converts a string representation of binary data into binary data
 &mdash; the reverse of <CODE
CLASS="FUNCTION"
>PQescapeBytea</CODE
>. This
 is needed when retrieving <TT
CLASS="TYPE"
>bytea</TT
> data in text format,
 but not when retrieving it in binary format.

<PRE
CLASS="SYNOPSIS"
>unsigned char *PQunescapeBytea(const unsigned char *from, size_t *to_length);</PRE
>
 The <TT
CLASS="PARAMETER"
>from</TT
> parameter points to a string
 such as might be returned by <CODE
CLASS="FUNCTION"
>PQgetvalue</CODE
> when applied
 to a <TT
CLASS="TYPE"
>bytea</TT
> column. <CODE
CLASS="FUNCTION"
>PQunescapeBytea</CODE
>
 converts this string representation into its binary representation.
 It returns a pointer to a buffer allocated with
 <CODE
CLASS="FUNCTION"
>malloc()</CODE
>, or <TT
CLASS="SYMBOL"
>NULL</TT
> on error, and puts the size of
 the buffer in <TT
CLASS="PARAMETER"
>to_length</TT
>. The result must be
 freed using <CODE
CLASS="FUNCTION"
>PQfreemem</CODE
> when it is no longer needed.
 This conversion is not exactly the inverse of
 <CODE
CLASS="FUNCTION"
>PQescapeBytea</CODE
>, because the string is not expected
 to be "escaped" when received from <CODE
CLASS="FUNCTION"
>PQgetvalue</CODE
>.
 In particular this means there is no need for string quoting considerations,
 and so no need for a <TT
CLASS="STRUCTNAME"
>PGconn</TT
> parameter.
 </DD
></DL
></DIV
></DIV
></DIV
><DIV
CLASS="NAVFOOTER"
><HR
ALIGN="LEFT"
WIDTH="100%"><TABLE
SUMMARY="Footer navigation table"
WIDTH="100%"
BORDER="0"
CELLPADDING="0"
CELLSPACING="0"
><TR
><TD
WIDTH="33%"
ALIGN="left"
VALIGN="top"
><A
HREF="libpq-status.html"
ACCESSKEY="P"
>Prev</A
></TD
><TD
WIDTH="34%"
ALIGN="center"
VALIGN="top"
><A
HREF="index.html"
ACCESSKEY="H"
>Home</A
></TD
><TD
WIDTH="33%"
ALIGN="right"
VALIGN="top"
><A
HREF="libpq-async.html"
ACCESSKEY="N"
>Next</A
></TD
></TR
><TR
><TD
WIDTH="33%"
ALIGN="left"
VALIGN="top"
>Connection Status Functions</TD
><TD
WIDTH="34%"
ALIGN="center"
VALIGN="top"
><A
HREF="libpq.html"
ACCESSKEY="U"
>Up</A
></TD
><TD
WIDTH="33%"
ALIGN="right"
VALIGN="top"
>Asynchronous Command Processing</TD
></TR
></TABLE
></DIV
></BODY
></HTML
>

${this.title}

Code Editor : libpq-exec.html