Re: Semantics of pg_file_settings view

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Sawada Masahiko <sawada(dot)mshk(at)gmail(dot)com>
Cc: Robert Haas <robertmhaas(at)gmail(dot)com>, "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Semantics of pg_file_settings view
Date: 2015-06-28 15:46:42
Message-ID: 19663.1435506402@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Sawada Masahiko <sawada(dot)mshk(at)gmail(dot)com> writes:
> On Mon, Jun 29, 2015 at 12:01 AM, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
>> er ... what?

> Sorry for confusing you.
> Anyway I meant that I got SEGV after applied WIP patch, and the cause
> is the above changes.
> The case is following.
> 1. Add "port = 6543" to postgresql.conf and restart server.
> 2. Remove that added line from postgresql.conf
> 3. Reload.
> Got SEGV.

Oh, okay. I'll check, thanks for noticing it!

regards, tom lane

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Simon Riggs 2015-06-28 15:56:47 Re: drop/truncate table sucks for large values of shared buffers
Previous Message Sawada Masahiko 2015-06-28 15:44:18 Re: Semantics of pg_file_settings view