Keep me update every new development
The following documentation comment has been logged on the website: Page: https://www.postgresql.org/docs/9.1/static/sql-listen.html Description: Keep me update every new development
Re: Keep me update every new development
On Sunday, March 18, 2018, PG Doc comments form wrote: > The following documentation comment has been logged on the website: > > Page: https://www.postgresql.org/docs/9.1/static/sql-listen.html > Description: > > Keep me update every new development > Sorry, listen/notify only works within the database. You'll need to setup something custom if you want to keep abreast of changes to the product itself or its documentation. Monitoring the mailing lists or the git repo itself is your best bet. David J.
float and float(p) missing from table 8.1
The following documentation comment has been logged on the website: Page: https://www.postgresql.org/docs/10/static/datatype.html Description: Maybe it is intentional, but the float and float(p) data types are missing from table 8.1 (https://www.postgresql.org/docs/10/static/datatype.html#DATATYPE-TABLE). float4 and float8 are listed.
Re: Synopsis of SELECT statement: UNION, INTERSECTION, EXCEPT
As a first step we could do something like:
basic_select_statement is:
> SELECT [ ALL | DISTINCT [ ON ( expression [, ...] ) ] ]
> [ * | expression [ [ AS ] output_name ] [, ...] ]
> [ FROM from_item [, ...] ]
> [ WHERE condition ]
> [ GROUP BY grouping_element [, ...] ]
> [ HAVING condition [, ...] ]
> [ WINDOW window_name AS ( window_definition ) [, ...] ]
>
full_select_statement is basic_select_statement with the following
possible additional clauses tacked onto the end:
[ ORDER BY expression [ ASC | DESC | USING operator ] [ NULLS { FIRST |
> LAST } ] [, ...] ]
> [ LIMIT { count | ALL } ]
> [ OFFSET start [ ROW | ROWS ] ]
> [ FETCH { FIRST | NEXT } [ count ] { ROW | ROWS } ONLY ]
> [ FOR { UPDATE | NO KEY UPDATE | SHARE | KEY SHARE } [ OF table_name
> [, ...] ] [ NOWAIT | SKIP LOCKED ] [...] ]
>
> and that's still not right because ORDER BY et al can't be attached to a
> select_stmt that's the argument of a set operation, so really we'd need
> a couple of levels of nonterminals before we get down to the basic
> "SELECT expression FROM ..." part. Nor has the use of parentheses been
> mentioned yet.
>
Then we can define the set clauses in terms of basic_select_stmt and
parentheses-surrounded full_select_stmt. The result of the set clause is
itself a type of basic_select_statement which can be made full by adding
one or more of the additional clauses, including ORDER BY.
David J.
Re: Postgres 10 and the pg_ctl "--wait" option
This seems to be different behaviour between pg9.5 and pg10. Pg9.5 does not give a connection error once "pg_ctl --wait ..." finishes. So I've moved this to the pgsql-bugs list. Greg On Fri, 2 Mar 2018 at 17:04 Greg k wrote: > In PostreSql 10, the documentation for pg_ctl and the "--wait" option says > "Startup is considered complete when the PID file indicates that the server > is ready to accept connections." > > When I do a point-in-time recovery followed by a start with > "/usr/pgsql-10/bin/pg_ctl start -D /data -w -t 86400", I then try to > connect immediately after pg_ctl finishes. But I get a connection error > "psql: FATAL: the database system is starting up" . It seems the > postmaster.pid file state goes from 'starting' to 'standby' to 'ready' but > pg_ctl is saying the server is ready to accept connections when the > postmaster.pid file says 'standby'. Am I misunderstanding the documentation? > > Thanks, > Greg >
