Re: Wrong link for FETCH FIRST in pg13 release notes

On Fri, May 22, 2020 at 12:12:48AM +0200, Erwin Brandstetter wrote: > Here: > https://www.postgresql.org/docs/13/release-13.html#id-1.11.6.5.5.5 > > > Allow FETCH FIRST to use WITH TIES to return any additional rows that match > the last result row (Surafel Temesgen) > > The link, by mistake, goe

Re: explanation for random_page_cost is outdated

On Mon, Apr 27, 2020 at 12:16:30PM -0400, Bruce Momjian wrote: > On Mon, Apr 27, 2020 at 06:02:41AM +0200, Pavel Stehule wrote: > >  >  Storage that has a low random read cost relative to sequential, e.g. > > solid-state drives, might also be better modeled with a value that is > > close >

Re: 11.7 Indexes on Expressions: editorial correction

On Tue, May 19, 2020 at 10:32:01AM -0400, Tom Lane wrote: > PG Doc comments form writes: > > The paragraph that begins "If we were to declare this index UNIQUE,..." > > refers to the index test1_lower_col1_idx, not to the test1_uniq_int index it > > currently follows. It would appear the latter ex

Re: pgsql: doc: add examples of creative use of unique expression indexes

On Mon, Apr 20, 2020 at 08:31:29PM -0400, Bruce Momjian wrote: > On Mon, Apr 20, 2020 at 04:21:32PM -0400, Tom Lane wrote: > > [ sorry, I'd lost track of this thread ] > > > > Bruce Momjian writes: > > > I now remember that I wrote the first IS NULL in: > > > CREATE UNIQUE INDEX tests_target_on

Wrong link for FETCH FIRST in pg13 release notes

Here: https://www.postgresql.org/docs/13/release-13.html#id-1.11.6.5.5.5 > Allow FETCH FIRST to use WITH TIES to return any additional rows that match the last result row (Surafel Temesgen) The link, by mistake, goes to: https://www.postgresql.o

Problem

The following documentation comment has been logged on the website: Page: https://www.postgresql.org/docs/10/sql-createextension.html Description: Excuse me I'm having a problem that I cannot create an extension in the database, so would you mind helping me solve the problem. When I create extens