On 25 February 2013 12:48, Craig Ringer cr...@2ndquadrant.com wrote:
However, the thing I want most couldn't be provided by this patch
because it seems to be a deeper server limitation: the ability to get
typmod data from calculation results like
NUMERIC(8,3) '11.131' + NUMERIC(8,3)
Hi hackers,
Type info can be viewed with \d mytable, however often I'd like to see
the type (and typmod) info in SELECT queries with psql, similar to pgAdmin
III. For example:
my_db=# \pset type
my_db=# SELECT * FROM my_table;
gid | description| width
integer | character
Hi hackers,
I'm curios why argument names (argname) are not used in the DDL for
functions in pg_catalog, while they are are used throughout the
documentation. For example, the documentation for pg_read_file in
Table 9-60[1] has an SQL prototype:
pg_read_file(filename text, offset bigint, length
Hey hackers,
I routinely run SQL scripts using pgsql -f myscript.sql. If there is
an error mid-way in a large script file, due to the default
ON_ERROR_STOP=0, I see repeated ERROR: current transaction is
aborted, commands ignored until end of transaction block until the
end of the script. Often
Hey hackers,
I have a few concerns with the usability and documentation for
pg_restore (note: I'm on 8.3, but I've checked the documentation for 8.4).
In my attempts to restore a table (using -t) from a backup file with -v
(verbose) selected, I noticed a few things:
1. If a non-existent
