On Tue, 2020-02-04 at 08:59 +, PG Doc comments form wrote:
> SELECT a + b AS sum, c FROM table1 ORDER BY sum + c; -- wrong
>
> It took me a while to figure out how to do it properly so I propose to add
> the following (or similar) info:
>
> ---
> If you need to sort by this kind of e
On 2/4/20 3:34 AM, Magnus Hagander wrote:
> On Mon, Feb 3, 2020 at 9:59 PM Jonathan S. Katz wrote:
>> So, if there was something done to redirect people from specific
>> deprecated documentation pages historically, it was before my time. Most
>> of the redirects have been as general purposes ones
Greetings,
* Alvaro Herrera (alvhe...@2ndquadrant.com) wrote:
> On 2020-Feb-03, Jonathan S. Katz wrote:
>
> > So, if there was something done to redirect people from specific
> > deprecated documentation pages historically, it was before my time. Most
> > of the redirects have been as general pur
The following documentation comment has been logged on the website:
Page: https://www.postgresql.org/docs/9.5/queries-order.html
Description:
In https://www.postgresql.org/docs/9.5/queries-order.html it is said that
the following is intentionally not allowed:
```
SELECT a + b AS sum, c FROM tabl
The following documentation comment has been logged on the website:
Page: https://www.postgresql.org/docs/12/limits.html
Description:
Appendix K (PostgreSQL Limits) - doesn't mention the (btree) index row size
limits. I think that it should.
The following documentation comment has been logged on the website:
Page: https://www.postgresql.org/docs/9.4/explicit-locking.html
Description:
Hi
The "13.3.1. Table-level Locks" subsection mentions the following: "Once
acquired, a lock is normally held till end of transaction." (maybe we shoul
On Mon, Feb 3, 2020 at 9:59 PM Jonathan S. Katz wrote:
>
> On 2/3/20 3:42 PM, Bruce Momjian wrote:
> > On Thu, Jan 23, 2020 at 07:12:08PM -0500, R Ransbottom wrote:
> >> On Mon, Jan 20, 2020 at 12:23:48PM +0900, Ian Barwick wrote:
> >>> On 2020/01/19 12:56, R Ransbottom wrote:
> >>
> I would
