FOP issues warnings about them. These aren't even used, so just
remove them. For the ones that are actually used, we'll come up with
a different solution.
Discussion: https://www.postgresql.org/message-id/flat/
e29b580e-79ab-a371-5ea4-
6946e4d3af0b%402ndQuadrant.com
-
id="ecpg-type-timestamp-date">timestamp, date
+
timestamp, date
Here is a pattern for handling timestamp variables
-
id="ecpg-type-bytea">bytea
+
bytea
The handling of the bytea type is similar to
- >Create a Foreign Table for PostgreSQL CSV Logs
+ >Create a Foreign Table for PostgreSQL CSV Logs
One of the obvious uses for file_fdw is to make
-
id="sql-commit-prepared-examples-title">Examples
+
Examples
Commit the transaction identified by the transaction
identifier foobar:
-
id="sql-createforeigntable-compatibility-title">Compatibility
+
Compatibility
The CREATE FOREIGN TABLE command largely conforms to the
-
id="sql-createview-updatable-views-title">Updatable Views
+
Updatable Views
-
id="sql-do-examples-title">Examples
+
Examples
Grant all privileges on all views in schema public to
role webuser:
-
id="sql-prepare-transaction-examples-title">Examples
+
Examples
Prepare the current transaction for two-phase commit, using
foobar as the transaction identifier:
-
id="sql-rollback-prepared-examples-title">Examples
+
Examples
Roll back the transaction identified by the transaction
identifier foobar: