Linux server.kiran-academy.com 3.10.0-1160.108.1.el7.x86_64 #1 SMP Thu Jan 25 16:17:31 UTC 2024 x86_64
Apache/2.4.57 (Unix) OpenSSL/1.0.2k-fips
: 194.233.91.196 | : 216.73.216.172
Cant Read [ /etc/named.conf ]
7.4.32
finalho
www.github.com/MadExploits
Terminal
AUTO ROOT
Adminer
Backdoor Destroyer
Linux Exploit
Lock Shell
Lock File
Create User
CREATE RDP
PHP Mailer
BACKCONNECT
UNLOCK SHELL
HASH IDENTIFIER
CPANEL RESET
CREATE WP USER
README
+ Create Folder
+ Create File
/
usr /
share /
doc /
postgresql-9.2.24 /
html /
[ HOME SHELL ]
Name
Size
Permission
Action
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--
Delete
Unzip
Zip
${this.title}
Close
Code Editor : libpq-connect.html
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd"> <HTML ><HEAD ><TITLE >Database Connection Control 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="libpq - C Library" HREF="libpq.html"><LINK REL="NEXT" TITLE="Connection Status Functions" HREF="libpq-status.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="libpq - C Library" HREF="libpq.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. <SPAN CLASS="APPLICATION" >libpq</SPAN > - C Library</TD ><TD WIDTH="20%" ALIGN="right" VALIGN="top" ><A TITLE="Connection Status Functions" HREF="libpq-status.html" ACCESSKEY="N" >Next</A ></TD ></TR ></TABLE ><HR ALIGN="LEFT" WIDTH="100%"></DIV ><DIV CLASS="SECT1" ><H1 CLASS="SECT1" ><A NAME="LIBPQ-CONNECT" >31.1. Database Connection Control Functions</A ></H1 ><P > The following functions deal with making a connection to a <SPAN CLASS="PRODUCTNAME" >PostgreSQL</SPAN > backend server. An application program can have several backend connections open at one time. (One reason to do that is to access more than one database.) Each connection is represented by a <TT CLASS="STRUCTNAME" >PGconn</TT > object, which is obtained from the function <CODE CLASS="FUNCTION" >PQconnectdb</CODE >, <CODE CLASS="FUNCTION" >PQconnectdbParams</CODE >, or <CODE CLASS="FUNCTION" >PQsetdbLogin</CODE >. Note that these functions will always return a non-null object pointer, unless perhaps there is too little memory even to allocate the <TT CLASS="STRUCTNAME" >PGconn</TT > object. The <CODE CLASS="FUNCTION" >PQstatus</CODE > function should be called to check the return value for a successful connection before queries are sent via the connection object. <DIV CLASS="WARNING" ><P ></P ><TABLE CLASS="WARNING" BORDER="1" WIDTH="100%" ><TR ><TD ALIGN="CENTER" ><B >Warning</B ></TD ></TR ><TR ><TD ALIGN="LEFT" ><P > On Unix, forking a process with open libpq connections can lead to unpredictable results because the parent and child processes share the same sockets and operating system resources. For this reason, such usage is not recommended, though doing an <CODE CLASS="FUNCTION" >exec</CODE > from the child process to load a new executable is safe. </P ></TD ></TR ></TABLE ></DIV > </P><DIV CLASS="NOTE" ><BLOCKQUOTE CLASS="NOTE" ><P ><B >Note: </B > On Windows, there is a way to improve performance if a single database connection is repeatedly started and shutdown. Internally, libpq calls <CODE CLASS="FUNCTION" >WSAStartup()</CODE > and <CODE CLASS="FUNCTION" >WSACleanup()</CODE > for connection startup and shutdown, respectively. <CODE CLASS="FUNCTION" >WSAStartup()</CODE > increments an internal Windows library reference count which is decremented by <CODE CLASS="FUNCTION" >WSACleanup()</CODE >. When the reference count is just one, calling <CODE CLASS="FUNCTION" >WSACleanup()</CODE > frees all resources and all DLLs are unloaded. This is an expensive operation. To avoid this, an application can manually call <CODE CLASS="FUNCTION" >WSAStartup()</CODE > so resources will not be freed when the last database connection is closed. </P ></BLOCKQUOTE ></DIV ><P> <P ></P ></P><DIV CLASS="VARIABLELIST" ><DL ><DT ><A NAME="LIBPQ-PQCONNECTDBPARAMS" ></A ><CODE CLASS="FUNCTION" >PQconnectdbParams</CODE ></DT ><DD ><P > Makes a new connection to the database server. </P><PRE CLASS="SYNOPSIS" >PGconn *PQconnectdbParams(const char * const *keywords, const char * const *values, int expand_dbname);</PRE ><P> </P ><P > This function opens a new database connection using the parameters taken from two <TT CLASS="SYMBOL" >NULL</TT >-terminated arrays. The first, <TT CLASS="LITERAL" >keywords</TT >, is defined as an array of strings, each one being a key word. The second, <TT CLASS="LITERAL" >values</TT >, gives the value for each key word. Unlike <CODE CLASS="FUNCTION" >PQsetdbLogin</CODE > below, the parameter set can be extended without changing the function signature, so use of this function (or its nonblocking analogs <CODE CLASS="FUNCTION" >PQconnectStartParams</CODE > and <CODE CLASS="FUNCTION" >PQconnectPoll</CODE >) is preferred for new application programming. </P ><P > The currently recognized parameter key words are listed in <A HREF="libpq-connect.html#LIBPQ-PARAMKEYWORDS" >Section 31.1.2</A >. </P ><P > When <TT CLASS="LITERAL" >expand_dbname</TT > is non-zero, the <TT CLASS="PARAMETER" >dbname</TT > key word value is allowed to be recognized as a connection string. Only the first occurrence of <TT CLASS="PARAMETER" >dbname</TT > is expanded this way, any subsequent <TT CLASS="PARAMETER" >dbname</TT > value is processed as plain database name. More details on the possible connection string formats appear in <A HREF="libpq-connect.html#LIBPQ-CONNSTRING" >Section 31.1.1</A >. </P ><P > The passed arrays can be empty to use all default parameters, or can contain one or more parameter settings. They should be matched in length. Processing will stop with the last non-<TT CLASS="SYMBOL" >NULL</TT > element of the <TT CLASS="LITERAL" >keywords</TT > array. </P ><P > If any parameter is unspecified, then the corresponding environment variable (see <A HREF="libpq-envars.html" >Section 31.14</A >) is checked. If the environment variable is not set either, then the indicated built-in defaults are used. </P ><P > In general key words are processed from the beginning of these arrays in index order. The effect of this is that when key words are repeated, the last processed value is retained. Therefore, through careful placement of the <TT CLASS="PARAMETER" >dbname</TT > key word, it is possible to determine what may be overridden by a <TT CLASS="PARAMETER" >conninfo</TT > string, and what may not. </P ></DD ><DT ><A NAME="LIBPQ-PQCONNECTDB" ></A ><CODE CLASS="FUNCTION" >PQconnectdb</CODE ></DT ><DD ><P > Makes a new connection to the database server. </P><PRE CLASS="SYNOPSIS" >PGconn *PQconnectdb(const char *conninfo);</PRE ><P> </P ><P > This function opens a new database connection using the parameters taken from the string <TT CLASS="LITERAL" >conninfo</TT >. </P ><P > The passed string can be empty to use all default parameters, or it can contain one or more parameter settings separated by whitespace, or it can contain a <ACRONYM CLASS="ACRONYM" >URI</ACRONYM >. See <A HREF="libpq-connect.html#LIBPQ-CONNSTRING" >Section 31.1.1</A > for details. </P ></DD ><DT ><A NAME="LIBPQ-PQSETDBLOGIN" ></A ><CODE CLASS="FUNCTION" >PQsetdbLogin</CODE ></DT ><DD ><P > Makes a new connection to the database server. </P><PRE CLASS="SYNOPSIS" >PGconn *PQsetdbLogin(const char *pghost, const char *pgport, const char *pgoptions, const char *pgtty, const char *dbName, const char *login, const char *pwd);</PRE ><P> </P ><P > This is the predecessor of <CODE CLASS="FUNCTION" >PQconnectdb</CODE > with a fixed set of parameters. It has the same functionality except that the missing parameters will always take on default values. Write <TT CLASS="SYMBOL" >NULL</TT > or an empty string for any one of the fixed parameters that is to be defaulted. </P ><P > If the <TT CLASS="PARAMETER" >dbName</TT > contains an <TT CLASS="SYMBOL" >=</TT > sign or has a valid connection <ACRONYM CLASS="ACRONYM" >URI</ACRONYM > prefix, it is taken as a <TT CLASS="PARAMETER" >conninfo</TT > string in exactly the same way as if it had been passed to <CODE CLASS="FUNCTION" >PQconnectdb</CODE >, and the remaining parameters are then applied as specified for <CODE CLASS="FUNCTION" >PQconnectdbParams</CODE >. </P ></DD ><DT ><A NAME="LIBPQ-PQSETDB" ></A ><CODE CLASS="FUNCTION" >PQsetdb</CODE ></DT ><DD ><P > Makes a new connection to the database server. </P><PRE CLASS="SYNOPSIS" >PGconn *PQsetdb(char *pghost, char *pgport, char *pgoptions, char *pgtty, char *dbName);</PRE ><P> </P ><P > This is a macro that calls <CODE CLASS="FUNCTION" >PQsetdbLogin</CODE > with null pointers for the <TT CLASS="PARAMETER" >login</TT > and <TT CLASS="PARAMETER" >pwd</TT > parameters. It is provided for backward compatibility with very old programs. </P ></DD ><DT ><A NAME="LIBPQ-PQCONNECTSTARTPARAMS" ></A ><CODE CLASS="FUNCTION" >PQconnectStartParams</CODE ><BR><CODE CLASS="FUNCTION" >PQconnectStart</CODE ><BR><CODE CLASS="FUNCTION" >PQconnectPoll</CODE ></DT ><DD ><P > Make a connection to the database server in a nonblocking manner. </P><PRE CLASS="SYNOPSIS" >PGconn *PQconnectStartParams(const char * const *keywords, const char * const *values, int expand_dbname); PGconn *PQconnectStart(const char *conninfo); PostgresPollingStatusType PQconnectPoll(PGconn *conn);</PRE ><P> </P ><P > These three functions are used to open a connection to a database server such that your application's thread of execution is not blocked on remote I/O whilst doing so. The point of this approach is that the waits for I/O to complete can occur in the application's main loop, rather than down inside <CODE CLASS="FUNCTION" >PQconnectdbParams</CODE > or <CODE CLASS="FUNCTION" >PQconnectdb</CODE >, and so the application can manage this operation in parallel with other activities. </P ><P > With <CODE CLASS="FUNCTION" >PQconnectStartParams</CODE >, the database connection is made using the parameters taken from the <TT CLASS="LITERAL" >keywords</TT > and <TT CLASS="LITERAL" >values</TT > arrays, and controlled by <TT CLASS="LITERAL" >expand_dbname</TT >, as described above for <CODE CLASS="FUNCTION" >PQconnectdbParams</CODE >. </P ><P > With <CODE CLASS="FUNCTION" >PQconnectStart</CODE >, the database connection is made using the parameters taken from the string <TT CLASS="LITERAL" >conninfo</TT > as described above for <CODE CLASS="FUNCTION" >PQconnectdb</CODE >. </P ><P > Neither <CODE CLASS="FUNCTION" >PQconnectStartParams</CODE > nor <CODE CLASS="FUNCTION" >PQconnectStart</CODE > nor <CODE CLASS="FUNCTION" >PQconnectPoll</CODE > will block, so long as a number of restrictions are met: <P ></P ></P><UL ><LI ><P > The <TT CLASS="LITERAL" >hostaddr</TT > and <TT CLASS="LITERAL" >host</TT > parameters are used appropriately to ensure that name and reverse name queries are not made. See the documentation of these parameters in <A HREF="libpq-connect.html#LIBPQ-PARAMKEYWORDS" >Section 31.1.2</A > for details. </P ></LI ><LI ><P > If you call <CODE CLASS="FUNCTION" >PQtrace</CODE >, ensure that the stream object into which you trace will not block. </P ></LI ><LI ><P > You ensure that the socket is in the appropriate state before calling <CODE CLASS="FUNCTION" >PQconnectPoll</CODE >, as described below. </P ></LI ></UL ><P> </P ><P > Note: use of <CODE CLASS="FUNCTION" >PQconnectStartParams</CODE > is analogous to <CODE CLASS="FUNCTION" >PQconnectStart</CODE > shown below. </P ><P > To begin a nonblocking connection request, call <TT CLASS="LITERAL" >conn = PQconnectStart("<TT CLASS="REPLACEABLE" ><I >connection_info_string</I ></TT >")</TT >. If <TT CLASS="VARNAME" >conn</TT > is null, then <SPAN CLASS="APPLICATION" >libpq</SPAN > has been unable to allocate a new <TT CLASS="STRUCTNAME" >PGconn</TT > structure. Otherwise, a valid <TT CLASS="STRUCTNAME" >PGconn</TT > pointer is returned (though not yet representing a valid connection to the database). On return from <CODE CLASS="FUNCTION" >PQconnectStart</CODE >, call <TT CLASS="LITERAL" >status = PQstatus(conn)</TT >. If <TT CLASS="VARNAME" >status</TT > equals <TT CLASS="SYMBOL" >CONNECTION_BAD</TT >, <CODE CLASS="FUNCTION" >PQconnectStart</CODE > has failed. </P ><P > If <CODE CLASS="FUNCTION" >PQconnectStart</CODE > succeeds, the next stage is to poll <SPAN CLASS="APPLICATION" >libpq</SPAN > so that it can proceed with the connection sequence. Use <CODE CLASS="FUNCTION" >PQsocket(conn)</CODE > to obtain the descriptor of the socket underlying the database connection. Loop thus: If <CODE CLASS="FUNCTION" >PQconnectPoll(conn)</CODE > last returned <TT CLASS="SYMBOL" >PGRES_POLLING_READING</TT >, wait until the socket is ready to read (as indicated by <CODE CLASS="FUNCTION" >select()</CODE >, <CODE CLASS="FUNCTION" >poll()</CODE >, or similar system function). Then call <CODE CLASS="FUNCTION" >PQconnectPoll(conn)</CODE > again. Conversely, if <CODE CLASS="FUNCTION" >PQconnectPoll(conn)</CODE > last returned <TT CLASS="SYMBOL" >PGRES_POLLING_WRITING</TT >, wait until the socket is ready to write, then call <CODE CLASS="FUNCTION" >PQconnectPoll(conn)</CODE > again. If you have yet to call <CODE CLASS="FUNCTION" >PQconnectPoll</CODE >, i.e., just after the call to <CODE CLASS="FUNCTION" >PQconnectStart</CODE >, behave as if it last returned <TT CLASS="SYMBOL" >PGRES_POLLING_WRITING</TT >. Continue this loop until <CODE CLASS="FUNCTION" >PQconnectPoll(conn)</CODE > returns <TT CLASS="SYMBOL" >PGRES_POLLING_FAILED</TT >, indicating the connection procedure has failed, or <TT CLASS="SYMBOL" >PGRES_POLLING_OK</TT >, indicating the connection has been successfully made. </P ><P > At any time during connection, the status of the connection can be checked by calling <CODE CLASS="FUNCTION" >PQstatus</CODE >. If this call returns <TT CLASS="SYMBOL" >CONNECTION_BAD</TT >, then the connection procedure has failed; if the call returns <CODE CLASS="FUNCTION" >CONNECTION_OK</CODE >, then the connection is ready. Both of these states are equally detectable from the return value of <CODE CLASS="FUNCTION" >PQconnectPoll</CODE >, described above. Other states might also occur during (and only during) an asynchronous connection procedure. These indicate the current stage of the connection procedure and might be useful to provide feedback to the user for example. These statuses are: <P ></P ></P><DIV CLASS="VARIABLELIST" ><DL ><DT ><A NAME="LIBPQ-CONNECTION-STARTED" ></A ><TT CLASS="SYMBOL" >CONNECTION_STARTED</TT ></DT ><DD ><P > Waiting for connection to be made. </P ></DD ><DT ><A NAME="LIBPQ-CONNECTION-MADE" ></A ><TT CLASS="SYMBOL" >CONNECTION_MADE</TT ></DT ><DD ><P > Connection OK; waiting to send. </P ></DD ><DT ><A NAME="LIBPQ-CONNECTION-AWAITING-RESPONSE" ></A ><TT CLASS="SYMBOL" >CONNECTION_AWAITING_RESPONSE</TT ></DT ><DD ><P > Waiting for a response from the server. </P ></DD ><DT ><A NAME="LIBPQ-CONNECTION-AUTH-OK" ></A ><TT CLASS="SYMBOL" >CONNECTION_AUTH_OK</TT ></DT ><DD ><P > Received authentication; waiting for backend start-up to finish. </P ></DD ><DT ><A NAME="LIBPQ-CONNECTION-SSL-STARTUP" ></A ><TT CLASS="SYMBOL" >CONNECTION_SSL_STARTUP</TT ></DT ><DD ><P > Negotiating SSL encryption. </P ></DD ><DT ><A NAME="LIBPQ-CONNECTION-SETENV" ></A ><TT CLASS="SYMBOL" >CONNECTION_SETENV</TT ></DT ><DD ><P > Negotiating environment-driven parameter settings. </P ></DD ></DL ></DIV ><P> Note that, although these constants will remain (in order to maintain compatibility), an application should never rely upon these occurring in a particular order, or at all, or on the status always being one of these documented values. An application might do something like this: </P><PRE CLASS="PROGRAMLISTING" >switch(PQstatus(conn)) { case CONNECTION_STARTED: feedback = "Connecting..."; break; case CONNECTION_MADE: feedback = "Connected to server..."; break; . . . default: feedback = "Connecting..."; }</PRE ><P> </P ><P > The <TT CLASS="LITERAL" >connect_timeout</TT > connection parameter is ignored when using <CODE CLASS="FUNCTION" >PQconnectPoll</CODE >; it is the application's responsibility to decide whether an excessive amount of time has elapsed. Otherwise, <CODE CLASS="FUNCTION" >PQconnectStart</CODE > followed by a <CODE CLASS="FUNCTION" >PQconnectPoll</CODE > loop is equivalent to <CODE CLASS="FUNCTION" >PQconnectdb</CODE >. </P ><P > Note that if <CODE CLASS="FUNCTION" >PQconnectStart</CODE > returns a non-null pointer, you must call <CODE CLASS="FUNCTION" >PQfinish</CODE > when you are finished with it, in order to dispose of the structure and any associated memory blocks. This must be done even if the connection attempt fails or is abandoned. </P ></DD ><DT ><A NAME="LIBPQ-PQCONNDEFAULTS" ></A ><CODE CLASS="FUNCTION" >PQconndefaults</CODE ></DT ><DD ><P > Returns the default connection options. </P><PRE CLASS="SYNOPSIS" >PQconninfoOption *PQconndefaults(void); typedef struct { char *keyword; /* The keyword of the option */ char *envvar; /* Fallback environment variable name */ char *compiled; /* Fallback compiled in default value */ char *val; /* Option's current value, or NULL */ char *label; /* Label for field in connect dialog */ char *dispchar; /* Indicates how to display this field in a connect dialog. Values are: "" Display entered value as is "*" Password field - hide value "D" Debug option - don't show by default */ int dispsize; /* Field size in characters for dialog */ } PQconninfoOption;</PRE ><P> </P ><P > Returns a connection options array. This can be used to determine all possible <CODE CLASS="FUNCTION" >PQconnectdb</CODE > options and their current default values. The return value points to an array of <TT CLASS="STRUCTNAME" >PQconninfoOption</TT > structures, which ends with an entry having a null <TT CLASS="STRUCTFIELD" >keyword</TT > pointer. The null pointer is returned if memory could not be allocated. Note that the current default values (<TT CLASS="STRUCTFIELD" >val</TT > fields) will depend on environment variables and other context. Callers must treat the connection options data as read-only. </P ><P > After processing the options array, free it by passing it to <CODE CLASS="FUNCTION" >PQconninfoFree</CODE >. If this is not done, a small amount of memory is leaked for each call to <CODE CLASS="FUNCTION" >PQconndefaults</CODE >. </P ></DD ><DT ><A NAME="LIBPQ-PQCONNINFOPARSE" ></A ><CODE CLASS="FUNCTION" >PQconninfoParse</CODE ></DT ><DD ><P > Returns parsed connection options from the provided connection string. </P><PRE CLASS="SYNOPSIS" >PQconninfoOption *PQconninfoParse(const char *conninfo, char **errmsg);</PRE ><P> </P ><P > Parses a connection string and returns the resulting options as an array; or returns <TT CLASS="SYMBOL" >NULL</TT > if there is a problem with the connection string. This function can be used to extract the <CODE CLASS="FUNCTION" >PQconnectdb</CODE > options in the provided connection string. The return value points to an array of <TT CLASS="STRUCTNAME" >PQconninfoOption</TT > structures, which ends with an entry having a null <TT CLASS="STRUCTFIELD" >keyword</TT > pointer. </P ><P > All legal options will be present in the result array, but the <TT CLASS="LITERAL" >PQconninfoOption</TT > for any option not present in the connection string will have <TT CLASS="LITERAL" >val</TT > set to <TT CLASS="LITERAL" >NULL</TT >; default values are not inserted. </P ><P > If <TT CLASS="LITERAL" >errmsg</TT > is not <TT CLASS="SYMBOL" >NULL</TT >, then <TT CLASS="LITERAL" >*errmsg</TT > is set to <TT CLASS="SYMBOL" >NULL</TT > on success, else to a <CODE CLASS="FUNCTION" >malloc</CODE >'d error string explaining the problem. (It is also possible for <TT CLASS="LITERAL" >*errmsg</TT > to be set to <TT CLASS="SYMBOL" >NULL</TT > and the function to return <TT CLASS="SYMBOL" >NULL</TT >; this indicates an out-of-memory condition.) </P ><P > After processing the options array, free it by passing it to <CODE CLASS="FUNCTION" >PQconninfoFree</CODE >. If this is not done, some memory is leaked for each call to <CODE CLASS="FUNCTION" >PQconninfoParse</CODE >. Conversely, if an error occurs and <TT CLASS="LITERAL" >errmsg</TT > is not <TT CLASS="SYMBOL" >NULL</TT >, be sure to free the error string using <CODE CLASS="FUNCTION" >PQfreemem</CODE >. </P ></DD ><DT ><A NAME="LIBPQ-PQFINISH" ></A ><CODE CLASS="FUNCTION" >PQfinish</CODE ></DT ><DD ><P > Closes the connection to the server. Also frees memory used by the <TT CLASS="STRUCTNAME" >PGconn</TT > object. </P><PRE CLASS="SYNOPSIS" >void PQfinish(PGconn *conn);</PRE ><P> </P ><P > Note that even if the server connection attempt fails (as indicated by <CODE CLASS="FUNCTION" >PQstatus</CODE >), the application should call <CODE CLASS="FUNCTION" >PQfinish</CODE > to free the memory used by the <TT CLASS="STRUCTNAME" >PGconn</TT > object. The <TT CLASS="STRUCTNAME" >PGconn</TT > pointer must not be used again after <CODE CLASS="FUNCTION" >PQfinish</CODE > has been called. </P ></DD ><DT ><A NAME="LIBPQ-PQRESET" ></A ><CODE CLASS="FUNCTION" >PQreset</CODE ></DT ><DD ><P > Resets the communication channel to the server. </P><PRE CLASS="SYNOPSIS" >void PQreset(PGconn *conn);</PRE ><P> </P ><P > This function will close the connection to the server and attempt to reestablish a new connection to the same server, using all the same parameters previously used. This might be useful for error recovery if a working connection is lost. </P ></DD ><DT ><A NAME="LIBPQ-PQRESETSTART" ></A ><CODE CLASS="FUNCTION" >PQresetStart</CODE ><BR><CODE CLASS="FUNCTION" >PQresetPoll</CODE ></DT ><DD ><P > Reset the communication channel to the server, in a nonblocking manner. </P><PRE CLASS="SYNOPSIS" >int PQresetStart(PGconn *conn); PostgresPollingStatusType PQresetPoll(PGconn *conn);</PRE ><P> </P ><P > These functions will close the connection to the server and attempt to reestablish a new connection to the same server, using all the same parameters previously used. This can be useful for error recovery if a working connection is lost. They differ from <CODE CLASS="FUNCTION" >PQreset</CODE > (above) in that they act in a nonblocking manner. These functions suffer from the same restrictions as <CODE CLASS="FUNCTION" >PQconnectStartParams</CODE >, <CODE CLASS="FUNCTION" >PQconnectStart</CODE > and <CODE CLASS="FUNCTION" >PQconnectPoll</CODE >. </P ><P > To initiate a connection reset, call <CODE CLASS="FUNCTION" >PQresetStart</CODE >. If it returns 0, the reset has failed. If it returns 1, poll the reset using <CODE CLASS="FUNCTION" >PQresetPoll</CODE > in exactly the same way as you would create the connection using <CODE CLASS="FUNCTION" >PQconnectPoll</CODE >. </P ></DD ><DT ><A NAME="LIBPQ-PQPINGPARAMS" ></A ><CODE CLASS="FUNCTION" >PQpingParams</CODE ></DT ><DD ><P > <CODE CLASS="FUNCTION" >PQpingParams</CODE > reports the status of the server. It accepts connection parameters identical to those of <CODE CLASS="FUNCTION" >PQconnectdbParams</CODE >, described above. It is not, however, necessary to supply correct user name, password, or database name values to obtain the server status. </P><PRE CLASS="SYNOPSIS" >PGPing PQpingParams(const char * const *keywords, const char * const *values, int expand_dbname);</PRE ><P> The function returns one of the following values: <P ></P ></P><DIV CLASS="VARIABLELIST" ><DL ><DT ><A NAME="LIBPQ-PQPINGPARAMS-PQPING-OK" ></A ><TT CLASS="LITERAL" >PQPING_OK</TT ></DT ><DD ><P > The server is running and appears to be accepting connections. </P ></DD ><DT ><A NAME="LIBPQ-PQPINGPARAMS-PQPING-REJECT" ></A ><TT CLASS="LITERAL" >PQPING_REJECT</TT ></DT ><DD ><P > The server is running but is in a state that disallows connections (startup, shutdown, or crash recovery). </P ></DD ><DT ><A NAME="LIBPQ-PQPINGPARAMS-PQPING-NO-RESPONSE" ></A ><TT CLASS="LITERAL" >PQPING_NO_RESPONSE</TT ></DT ><DD ><P > The server could not be contacted. This might indicate that the server is not running, or that there is something wrong with the given connection parameters (for example, wrong port number), or that there is a network connectivity problem (for example, a firewall blocking the connection request). </P ></DD ><DT ><A NAME="LIBPQ-PQPINGPARAMS-PQPING-NO-ATTEMPT" ></A ><TT CLASS="LITERAL" >PQPING_NO_ATTEMPT</TT ></DT ><DD ><P > No attempt was made to contact the server, because the supplied parameters were obviously incorrect or there was some client-side problem (for example, out of memory). </P ></DD ></DL ></DIV ><P> </P ></DD ><DT ><A NAME="LIBPQ-PQPING" ></A ><CODE CLASS="FUNCTION" >PQping</CODE ></DT ><DD ><P > <CODE CLASS="FUNCTION" >PQping</CODE > reports the status of the server. It accepts connection parameters identical to those of <CODE CLASS="FUNCTION" >PQconnectdb</CODE >, described above. It is not, however, necessary to supply correct user name, password, or database name values to obtain the server status. </P><PRE CLASS="SYNOPSIS" >PGPing PQping(const char *conninfo);</PRE ><P> </P ><P > The return values are the same as for <CODE CLASS="FUNCTION" >PQpingParams</CODE >. </P ></DD ></DL ></DIV ><P> </P ><DIV CLASS="SECT2" ><H2 CLASS="SECT2" ><A NAME="LIBPQ-CONNSTRING" >31.1.1. Connection Strings</A ></H2 ><P > Several <SPAN CLASS="APPLICATION" >libpq</SPAN > functions parse a user-specified string to obtain connection parameters. There are two accepted formats for these strings: plain <TT CLASS="LITERAL" >keyword = value</TT > strings and <A HREF="http://www.ietf.org/rfc/rfc3986.txt" TARGET="_top" >RFC 3986</A > URIs. </P ><DIV CLASS="SECT3" ><H3 CLASS="SECT3" ><A NAME="AEN38669" >31.1.1.1. Keyword/Value Connection Strings</A ></H3 ><P > In the first format, each parameter setting is in the form <TT CLASS="LITERAL" >keyword = value</TT >. Spaces around the equal sign are optional. To write an empty value, or a value containing spaces, surround it with single quotes, e.g., <TT CLASS="LITERAL" >keyword = 'a value'</TT >. Single quotes and backslashes within the value must be escaped with a backslash, i.e., <TT CLASS="LITERAL" >\'</TT > and <TT CLASS="LITERAL" >\\</TT >. </P ><P > Example: </P><PRE CLASS="PROGRAMLISTING" >host=localhost port=5432 dbname=mydb connect_timeout=10</PRE ><P> </P ><P > The recognized parameter key words are listed in <A HREF="libpq-connect.html#LIBPQ-PARAMKEYWORDS" >Section 31.1.2</A >. </P ></DIV ><DIV CLASS="SECT3" ><H3 CLASS="SECT3" ><A NAME="AEN38680" >31.1.1.2. Connection URIs</A ></H3 ><P > The general form for a connection <ACRONYM CLASS="ACRONYM" >URI</ACRONYM > is: </P><PRE CLASS="SYNOPSIS" >postgresql://[user[:password]@][netloc][:port][/dbname][?param1=value1&...]</PRE ><P> </P ><P > The <ACRONYM CLASS="ACRONYM" >URI</ACRONYM > scheme designator can be either <TT CLASS="LITERAL" >postgresql://</TT > or <TT CLASS="LITERAL" >postgres://</TT >. Each of the <ACRONYM CLASS="ACRONYM" >URI</ACRONYM > parts is optional. The following examples illustrate valid <ACRONYM CLASS="ACRONYM" >URI</ACRONYM > syntax uses: </P><PRE CLASS="PROGRAMLISTING" >postgresql:// postgresql://localhost postgresql://localhost:5433 postgresql://localhost/mydb postgresql://user@localhost postgresql://user:secret@localhost postgresql://other@localhost/otherdb?connect_timeout=10&application_name=myapp</PRE ><P> Components of the hierarchical part of the <ACRONYM CLASS="ACRONYM" >URI</ACRONYM > can also be given as parameters. For example: </P><PRE CLASS="PROGRAMLISTING" >postgresql:///mydb?host=localhost&port=5433</PRE ><P> </P ><P > Percent-encoding may be used to include symbols with special meaning in any of the <ACRONYM CLASS="ACRONYM" >URI</ACRONYM > parts. </P ><P > Any connection parameters not corresponding to key words listed in <A HREF="libpq-connect.html#LIBPQ-PARAMKEYWORDS" >Section 31.1.2</A > are ignored and a warning message about them is sent to <TT CLASS="FILENAME" >stderr</TT >. </P ><P > For improved compatibility with JDBC connection <ACRONYM CLASS="ACRONYM" >URI</ACRONYM >s, instances of parameter <TT CLASS="LITERAL" >ssl=true</TT > are translated into <TT CLASS="LITERAL" >sslmode=require</TT >. </P ><P > The host part may be either host name or an IP address. To specify an IPv6 host address, enclose it in square brackets: </P><PRE CLASS="SYNOPSIS" >postgresql://[2001:db8::1234]/database</PRE ><P> </P ><P > The host component is interpreted as described for the parameter <A HREF="libpq-connect.html#LIBPQ-CONNECT-HOST" >host</A >. In particular, a Unix-domain socket connection is chosen if the host part is either empty or starts with a slash, otherwise a TCP/IP connection is initiated. Note, however, that the slash is a reserved character in the hierarchical part of the URI. So, to specify a non-standard Unix-domain socket directory, either omit the host specification in the URI and specify the host as a parameter, or percent-encode the path in the host component of the URI: </P><PRE CLASS="PROGRAMLISTING" >postgresql:///dbname?host=/var/lib/postgresql postgresql://%2Fvar%2Flib%2Fpostgresql/dbname</PRE ><P> </P ></DIV ></DIV ><DIV CLASS="SECT2" ><H2 CLASS="SECT2" ><A NAME="LIBPQ-PARAMKEYWORDS" >31.1.2. Parameter Key Words</A ></H2 ><P > The currently recognized parameter key words are: <P ></P ></P><DIV CLASS="VARIABLELIST" ><DL ><DT ><A NAME="LIBPQ-CONNECT-HOST" ></A ><TT CLASS="LITERAL" >host</TT ></DT ><DD ><P > Name of host to connect to. If this begins with a slash, it specifies Unix-domain communication rather than TCP/IP communication; the value is the name of the directory in which the socket file is stored. The default behavior when <TT CLASS="LITERAL" >host</TT > is not specified is to connect to a Unix-domain socket in <TT CLASS="FILENAME" >/tmp</TT > (or whatever socket directory was specified when <SPAN CLASS="PRODUCTNAME" >PostgreSQL</SPAN > was built). On machines without Unix-domain sockets, the default is to connect to <TT CLASS="LITERAL" >localhost</TT >. </P ></DD ><DT ><A NAME="LIBPQ-CONNECT-HOSTADDR" ></A ><TT CLASS="LITERAL" >hostaddr</TT ></DT ><DD ><P > Numeric IP address of host to connect to. This should be in the standard IPv4 address format, e.g., <TT CLASS="LITERAL" >172.28.40.9</TT >. If your machine supports IPv6, you can also use those addresses. TCP/IP communication is always used when a nonempty string is specified for this parameter. </P ><P > Using <TT CLASS="LITERAL" >hostaddr</TT > instead of <TT CLASS="LITERAL" >host</TT > allows the application to avoid a host name look-up, which might be important in applications with time constraints. However, a host name is required for Kerberos, GSSAPI, or SSPI authentication methods, as well as for <TT CLASS="LITERAL" >verify-full</TT > SSL certificate verification. The following rules are used: <P ></P ></P><UL ><LI ><P > If <TT CLASS="LITERAL" >host</TT > is specified without <TT CLASS="LITERAL" >hostaddr</TT >, a host name lookup occurs. </P ></LI ><LI ><P > If <TT CLASS="LITERAL" >hostaddr</TT > is specified without <TT CLASS="LITERAL" >host</TT >, the value for <TT CLASS="LITERAL" >hostaddr</TT > gives the server network address. The connection attempt will fail if the authentication method requires a host name. </P ></LI ><LI ><P > If both <TT CLASS="LITERAL" >host</TT > and <TT CLASS="LITERAL" >hostaddr</TT > are specified, the value for <TT CLASS="LITERAL" >hostaddr</TT > gives the server network address. The value for <TT CLASS="LITERAL" >host</TT > is ignored unless the authentication method requires it, in which case it will be used as the host name. </P ></LI ></UL ><P> Note that authentication is likely to fail if <TT CLASS="LITERAL" >host</TT > is not the name of the server at network address <TT CLASS="LITERAL" >hostaddr</TT >. Also, note that <TT CLASS="LITERAL" >host</TT > rather than <TT CLASS="LITERAL" >hostaddr</TT > is used to identify the connection in <TT CLASS="FILENAME" >~/.pgpass</TT > (see <A HREF="libpq-pgpass.html" >Section 31.15</A >). </P ><P > Without either a host name or host address, <SPAN CLASS="APPLICATION" >libpq</SPAN > will connect using a local Unix-domain socket; or on machines without Unix-domain sockets, it will attempt to connect to <TT CLASS="LITERAL" >localhost</TT >. </P ></DD ><DT ><A NAME="LIBPQ-CONNECT-PORT" ></A ><TT CLASS="LITERAL" >port</TT ></DT ><DD ><P > Port number to connect to at the server host, or socket file name extension for Unix-domain connections. </P ></DD ><DT ><A NAME="LIBPQ-CONNECT-DBNAME" ></A ><TT CLASS="LITERAL" >dbname</TT ></DT ><DD ><P > The database name. Defaults to be the same as the user name. In certain contexts, the value is checked for extended formats; see <A HREF="libpq-connect.html#LIBPQ-CONNSTRING" >Section 31.1.1</A > for more details on those. </P ></DD ><DT ><A NAME="LIBPQ-CONNECT-USER" ></A ><TT CLASS="LITERAL" >user</TT ></DT ><DD ><P > <SPAN CLASS="PRODUCTNAME" >PostgreSQL</SPAN > user name to connect as. Defaults to be the same as the operating system name of the user running the application. </P ></DD ><DT ><A NAME="LIBPQ-CONNECT-PASSWORD" ></A ><TT CLASS="LITERAL" >password</TT ></DT ><DD ><P > Password to be used if the server demands password authentication. </P ></DD ><DT ><A NAME="LIBPQ-CONNECT-CONNECT-TIMEOUT" ></A ><TT CLASS="LITERAL" >connect_timeout</TT ></DT ><DD ><P > Maximum wait for connection, in seconds (write as a decimal integer string). Zero or not specified means wait indefinitely. It is not recommended to use a timeout of less than 2 seconds. </P ></DD ><DT ><A NAME="LIBPQ-CONNECT-CLIENT-ENCODING" ></A ><TT CLASS="LITERAL" >client_encoding</TT ></DT ><DD ><P > This sets the <TT CLASS="VARNAME" >client_encoding</TT > configuration parameter for this connection. In addition to the values accepted by the corresponding server option, you can use <TT CLASS="LITERAL" >auto</TT > to determine the right encoding from the current locale in the client (<TT CLASS="ENVAR" >LC_CTYPE</TT > environment variable on Unix systems). </P ></DD ><DT ><A NAME="LIBPQ-CONNECT-OPTIONS" ></A ><TT CLASS="LITERAL" >options</TT ></DT ><DD ><P > Adds command-line options to send to the server at run-time. For example, setting this to <TT CLASS="LITERAL" >-c geqo=off</TT > sets the session's value of the <TT CLASS="VARNAME" >geqo</TT > parameter to <TT CLASS="LITERAL" >off</TT >. For a detailed discussion of the available options, consult <A HREF="runtime-config.html" >Chapter 18</A >. </P ></DD ><DT ><A NAME="LIBPQ-CONNECT-APPLICATION-NAME" ></A ><TT CLASS="LITERAL" >application_name</TT ></DT ><DD ><P > Specifies a value for the <A HREF="runtime-config-logging.html#GUC-APPLICATION-NAME" >application_name</A > configuration parameter. </P ></DD ><DT ><A NAME="LIBPQ-CONNECT-FALLBACK-APPLICATION-NAME" ></A ><TT CLASS="LITERAL" >fallback_application_name</TT ></DT ><DD ><P > Specifies a fallback value for the <A HREF="runtime-config-logging.html#GUC-APPLICATION-NAME" >application_name</A > configuration parameter. This value will be used if no value has been given for <TT CLASS="LITERAL" >application_name</TT > via a connection parameter or the <TT CLASS="ENVAR" >PGAPPNAME</TT > environment variable. Specifying a fallback name is useful in generic utility programs that wish to set a default application name but allow it to be overridden by the user. </P ></DD ><DT ><A NAME="LIBPQ-KEEPALIVES" ></A ><TT CLASS="LITERAL" >keepalives</TT ></DT ><DD ><P > Controls whether client-side TCP keepalives are used. The default value is 1, meaning on, but you can change this to 0, meaning off, if keepalives are not wanted. This parameter is ignored for connections made via a Unix-domain socket. </P ></DD ><DT ><A NAME="LIBPQ-KEEPALIVES-IDLE" ></A ><TT CLASS="LITERAL" >keepalives_idle</TT ></DT ><DD ><P > Controls the number of seconds of inactivity after which TCP should send a keepalive message to the server. A value of zero uses the system default. This parameter is ignored for connections made via a Unix-domain socket, or if keepalives are disabled. It is only supported on systems where <TT CLASS="SYMBOL" >TCP_KEEPIDLE</TT > or an equivalent socket option is available, and on Windows; on other systems, it has no effect. </P ></DD ><DT ><A NAME="LIBPQ-KEEPALIVES-INTERVAL" ></A ><TT CLASS="LITERAL" >keepalives_interval</TT ></DT ><DD ><P > Controls the number of seconds after which a TCP keepalive message that is not acknowledged by the server should be retransmitted. A value of zero uses the system default. This parameter is ignored for connections made via a Unix-domain socket, or if keepalives are disabled. It is only supported on systems where <TT CLASS="SYMBOL" >TCP_KEEPINTVL</TT > or an equivalent socket option is available, and on Windows; on other systems, it has no effect. </P ></DD ><DT ><A NAME="LIBPQ-KEEPALIVES-COUNT" ></A ><TT CLASS="LITERAL" >keepalives_count</TT ></DT ><DD ><P > Controls the number of TCP keepalives that can be lost before the client's connection to the server is considered dead. A value of zero uses the system default. This parameter is ignored for connections made via a Unix-domain socket, or if keepalives are disabled. It is only supported on systems where <TT CLASS="SYMBOL" >TCP_KEEPCNT</TT > or an equivalent socket option is available; on other systems, it has no effect. </P ></DD ><DT ><A NAME="LIBPQ-CONNECT-TTY" ></A ><TT CLASS="LITERAL" >tty</TT ></DT ><DD ><P > Ignored (formerly, this specified where to send server debug output). </P ></DD ><DT ><A NAME="LIBPQ-CONNECT-SSLMODE" ></A ><TT CLASS="LITERAL" >sslmode</TT ></DT ><DD ><P > This option determines whether or with what priority a secure <ACRONYM CLASS="ACRONYM" >SSL</ACRONYM > TCP/IP connection will be negotiated with the server. There are six modes: <P ></P ></P><DIV CLASS="VARIABLELIST" ><DL ><DT ><TT CLASS="LITERAL" >disable</TT ></DT ><DD ><P > only try a non-<ACRONYM CLASS="ACRONYM" >SSL</ACRONYM > connection </P ></DD ><DT ><TT CLASS="LITERAL" >allow</TT ></DT ><DD ><P > first try a non-<ACRONYM CLASS="ACRONYM" >SSL</ACRONYM > connection; if that fails, try an <ACRONYM CLASS="ACRONYM" >SSL</ACRONYM > connection </P ></DD ><DT ><TT CLASS="LITERAL" >prefer</TT > (default)</DT ><DD ><P > first try an <ACRONYM CLASS="ACRONYM" >SSL</ACRONYM > connection; if that fails, try a non-<ACRONYM CLASS="ACRONYM" >SSL</ACRONYM > connection </P ></DD ><DT ><TT CLASS="LITERAL" >require</TT ></DT ><DD ><P > only try an <ACRONYM CLASS="ACRONYM" >SSL</ACRONYM > connection. If a root CA file is present, verify the certificate in the same way as if <TT CLASS="LITERAL" >verify-ca</TT > was specified </P ></DD ><DT ><TT CLASS="LITERAL" >verify-ca</TT ></DT ><DD ><P > only try an <ACRONYM CLASS="ACRONYM" >SSL</ACRONYM > connection, and verify that the server certificate is issued by a trusted certificate authority (<ACRONYM CLASS="ACRONYM" >CA</ACRONYM >) </P ></DD ><DT ><TT CLASS="LITERAL" >verify-full</TT ></DT ><DD ><P > only try an <ACRONYM CLASS="ACRONYM" >SSL</ACRONYM > connection, verify that the server certificate is issued by a trusted <ACRONYM CLASS="ACRONYM" >CA</ACRONYM > and that the server host name matches that in the certificate </P ></DD ></DL ></DIV ><P> See <A HREF="libpq-ssl.html" >Section 31.18</A > for a detailed description of how these options work. </P ><P > <TT CLASS="LITERAL" >sslmode</TT > is ignored for Unix domain socket communication. If <SPAN CLASS="PRODUCTNAME" >PostgreSQL</SPAN > is compiled without SSL support, using options <TT CLASS="LITERAL" >require</TT >, <TT CLASS="LITERAL" >verify-ca</TT >, or <TT CLASS="LITERAL" >verify-full</TT > will cause an error, while options <TT CLASS="LITERAL" >allow</TT > and <TT CLASS="LITERAL" >prefer</TT > will be accepted but <SPAN CLASS="APPLICATION" >libpq</SPAN > will not actually attempt an <ACRONYM CLASS="ACRONYM" >SSL</ACRONYM > connection. </P ></DD ><DT ><A NAME="LIBPQ-CONNECT-REQUIRESSL" ></A ><TT CLASS="LITERAL" >requiressl</TT ></DT ><DD ><P > This option is deprecated in favor of the <TT CLASS="LITERAL" >sslmode</TT > setting. </P ><P > If set to 1, an <ACRONYM CLASS="ACRONYM" >SSL</ACRONYM > connection to the server is required (this is equivalent to <TT CLASS="LITERAL" >sslmode</TT > <TT CLASS="LITERAL" >require</TT >). <SPAN CLASS="APPLICATION" >libpq</SPAN > will then refuse to connect if the server does not accept an <ACRONYM CLASS="ACRONYM" >SSL</ACRONYM > connection. If set to 0 (default), <SPAN CLASS="APPLICATION" >libpq</SPAN > will negotiate the connection type with the server (equivalent to <TT CLASS="LITERAL" >sslmode</TT > <TT CLASS="LITERAL" >prefer</TT >). This option is only available if <SPAN CLASS="PRODUCTNAME" >PostgreSQL</SPAN > is compiled with SSL support. </P ></DD ><DT ><A NAME="LIBPQ-CONNECT-SSLCOMPRESSION" ></A ><TT CLASS="LITERAL" >sslcompression</TT ></DT ><DD ><P > If set to 1 (default), data sent over SSL connections will be compressed (this requires <SPAN CLASS="PRODUCTNAME" >OpenSSL</SPAN > version 0.9.8 or later). If set to 0, compression will be disabled (this requires <SPAN CLASS="PRODUCTNAME" >OpenSSL</SPAN > 1.0.0 or later). This parameter is ignored if a connection without SSL is made, or if the version of <SPAN CLASS="PRODUCTNAME" >OpenSSL</SPAN > used does not support it. </P ><P > Compression uses CPU time, but can improve throughput if the network is the bottleneck. Disabling compression can improve response time and throughput if CPU performance is the limiting factor. </P ></DD ><DT ><A NAME="LIBPQ-CONNECT-SSLCERT" ></A ><TT CLASS="LITERAL" >sslcert</TT ></DT ><DD ><P > This parameter specifies the file name of the client SSL certificate, replacing the default <TT CLASS="FILENAME" >~/.postgresql/postgresql.crt</TT >. This parameter is ignored if an SSL connection is not made. </P ></DD ><DT ><A NAME="LIBPQ-CONNECT-SSLKEY" ></A ><TT CLASS="LITERAL" >sslkey</TT ></DT ><DD ><P > This parameter specifies the location for the secret key used for the client certificate. It can either specify a file name that will be used instead of the default <TT CLASS="FILENAME" >~/.postgresql/postgresql.key</TT >, or it can specify a key obtained from an external <SPAN CLASS="QUOTE" >"engine"</SPAN > (engines are <SPAN CLASS="PRODUCTNAME" >OpenSSL</SPAN > loadable modules). An external engine specification should consist of a colon-separated engine name and an engine-specific key identifier. This parameter is ignored if an SSL connection is not made. </P ></DD ><DT ><A NAME="LIBPQ-CONNECT-SSLROOTCERT" ></A ><TT CLASS="LITERAL" >sslrootcert</TT ></DT ><DD ><P > This parameter specifies the name of a file containing SSL certificate authority (<ACRONYM CLASS="ACRONYM" >CA</ACRONYM >) certificate(s). If the file exists, the server's certificate will be verified to be signed by one of these authorities. The default is <TT CLASS="FILENAME" >~/.postgresql/root.crt</TT >. </P ></DD ><DT ><A NAME="LIBPQ-CONNECT-SSLCRL" ></A ><TT CLASS="LITERAL" >sslcrl</TT ></DT ><DD ><P > This parameter specifies the file name of the SSL certificate revocation list (CRL). Certificates listed in this file, if it exists, will be rejected while attempting to authenticate the server's certificate. The default is <TT CLASS="FILENAME" >~/.postgresql/root.crl</TT >. </P ></DD ><DT ><A NAME="LIBPQ-CONNECT-REQUIREPEER" ></A ><TT CLASS="LITERAL" >requirepeer</TT ></DT ><DD ><P > This parameter specifies the operating-system user name of the server, for example <TT CLASS="LITERAL" >requirepeer=postgres</TT >. When making a Unix-domain socket connection, if this parameter is set, the client checks at the beginning of the connection that the server process is running under the specified user name; if it is not, the connection is aborted with an error. This parameter can be used to provide server authentication similar to that available with SSL certificates on TCP/IP connections. (Note that if the Unix-domain socket is in <TT CLASS="FILENAME" >/tmp</TT > or another publicly writable location, any user could start a server listening there. Use this parameter to ensure that you are connected to a server run by a trusted user.) This option is only supported on platforms for which the <TT CLASS="LITERAL" >peer</TT > authentication method is implemented; see <A HREF="auth-methods.html#AUTH-PEER" >Section 19.3.7</A >. </P ></DD ><DT ><A NAME="LIBPQ-CONNECT-KRBSRVNAME" ></A ><TT CLASS="LITERAL" >krbsrvname</TT ></DT ><DD ><P > Kerberos service name to use when authenticating with Kerberos 5 or GSSAPI. This must match the service name specified in the server configuration for Kerberos authentication to succeed. (See also <A HREF="auth-methods.html#KERBEROS-AUTH" >Section 19.3.5</A > and <A HREF="auth-methods.html#GSSAPI-AUTH" >Section 19.3.3</A >.) </P ></DD ><DT ><A NAME="LIBPQ-CONNECT-GSSLIB" ></A ><TT CLASS="LITERAL" >gsslib</TT ></DT ><DD ><P > GSS library to use for GSSAPI authentication. Only used on Windows. Set to <TT CLASS="LITERAL" >gssapi</TT > to force libpq to use the GSSAPI library for authentication instead of the default SSPI. </P ></DD ><DT ><A NAME="LIBPQ-CONNECT-SERVICE" ></A ><TT CLASS="LITERAL" >service</TT ></DT ><DD ><P > Service name to use for additional parameters. It specifies a service name in <TT CLASS="FILENAME" >pg_service.conf</TT > that holds additional connection parameters. This allows applications to specify only a service name so connection parameters can be centrally maintained. See <A HREF="libpq-pgservice.html" >Section 31.16</A >. </P ></DD ></DL ></DIV ><P> </P ></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.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-status.html" ACCESSKEY="N" >Next</A ></TD ></TR ><TR ><TD WIDTH="33%" ALIGN="left" VALIGN="top" ><SPAN CLASS="APPLICATION" >libpq</SPAN > - C Library</TD ><TD WIDTH="34%" ALIGN="center" VALIGN="top" ><A HREF="libpq.html" ACCESSKEY="U" >Up</A ></TD ><TD WIDTH="33%" ALIGN="right" VALIGN="top" >Connection Status Functions</TD ></TR ></TABLE ></DIV ></BODY ></HTML >
Close