Re: [DOCS] The multi-column index create fail

You need to install the btree_gin extension, with CREATE EXTENSION, in each database that you want such indexes. See: https://www.postgresql.org/docs/current/static/btree-gin.html and https://www.postgresql.org/docs/current/static/sql-createextension.html On Mon, Nov 6, 2017 at 3:47 AM,

Re: [DOCS] Wrong description in "13.2.1. Read Committed Isolation Level"

On Fri, Oct 13, 2017 at 12:17 PM, wrote: > The following documentation comment has been logged on the website: > > Page: https://www.postgresql.org/docs/10/static/transaction-iso.html > Description: > > In section 13.2.1. Read Committed Isolation Level the document >

[DOCS] Changes in serial / sequence introduced in Postgresql 10

tity columns feature and I think it would be good to be somewhere in the documentation or the release notes - assuming that it was intentional. Pantelis Theodosiou

Re: [DOCS] Need help finding all possible parameters for wal_level

if you intend to use one. > > On Fri, Sep 1, 2017 at 10:43 AM, Pantelis Theodosiou <yperc...@gmail.com> > wrote: > >> >> >> On Fri, Sep 1, 2017 at 3:36 PM, None <espressobean...@gmail.com> wrote: >> >>> Hi, >>> >>> I'm sear

Re: [DOCS] Need help finding all possible parameters for wal_level

On Fri, Sep 1, 2017 at 3:36 PM, None wrote: > Hi, > > I'm searching for all of the possible parameters for setting the > "wal_level" outlined in the PostgreSQL Streaming Replication article: > > https://wiki.postgresql.org/wiki/Streaming_Replication > > I currently see

Re: [DOCS] Table names in upper case

actly the documented behaviour (9.5.4, Ubuntu): x=# CREATE TABLE CLIENT(ID INTEGER, NAME TEXT); CREATE TABLE x=# select * from client ; id | name +-- (0 rows) x=# select * from "CLIENT" ; ERROR: relation "CLIENT" does not exist LINE 1: select * from "CLIENT" ; ^ x=# Pantelis Theodosiou

Re: [DOCS] CTEs modifying the same table more than once

PM, Marko Tiikkaja <ma...@joh.to> wrote: > On 2016-10-01 13:13, Pantelis Theodosiou wrote: > >> I answered that this is unpredictable behaviour but the docs state only >> the >> update-update and update-delete cases explicitly and the general wording >> is >&

[DOCS] CTEs modifying the same table more than once

our but the docs state only the update-update and update-delete cases explicitly and the general wording is about 2 updates. I suggest that the insert-update and insert-delete cases are added as well (assuming that my understanding is correct and that these also result in unpredictable results). Pante