On Mon, Jul 31, 2017 at 11:48 AM, Tom Lane wrote:
> Peter Eisentraut writes:
>> On 7/21/17 06:18, gorka@openbravo.com wrote:
>>> In "Linux" section, show an example of setting shmmax to 16GB,
>>> when this
>>> change is not needed from pg 9.3.
>>>
>>> Maybe just remove to avoid confusion?
>>
Peter Eisentraut writes:
> On 7/21/17 06:18, gorka@openbravo.com wrote:
>> In "Linux" section, show an example of setting shmmax to 16GB,
>> when this
>> change is not needed from pg 9.3.
>>
>> Maybe just remove to avoid confusion?
>> Maybe also shmall also not needed ?
> It's still needed
On 7/27/17 09:24, hol...@jakobs.com wrote:
> The following documentation comment has been logged on the website:
>
> Page: https://www.postgresql.org/docs/9.6/static/pgupgrade.html
> Description:
>
> https://www.postgresql.org/docs/9.6/static/pgupgrade.html states that
> junction points are creat
On 7/21/17 06:18, gorka@openbravo.com wrote:
> The following documentation comment has been logged on the website:
>
> Page: https://www.postgresql.org/docs/9.5/static/kernel-resources.html
> Description:
>
> Hi,
>
> I'm refer to this document:
> https://www.postgresql.org/docs/9.5/static/ke
On Mon, Jul 31, 2017 at 6:16 AM, wrote:
> The following documentation comment has been logged on the website:
>
> Page: https://www.postgresql.org/docs/9.6/static/wal-configuration.html
> Description:
>
> In this section:
>
> "At checkpoint time, all dirty data pages are flushed to disk and a
> s
The following documentation comment has been logged on the website:
Page: https://www.postgresql.org/docs/9.6/static/wal-configuration.html
Description:
In this section:
"At checkpoint time, all dirty data pages are flushed to disk and a special
checkpoint record is written to the log file. (The
