On 2018-11-07 09:37:37 -0500, Andrew Dunstan wrote:
>
> On 11/7/18 9:11 AM, Tomas Vondra wrote:
> >
> > On 11/7/18 2:47 PM, John Naylor wrote:
> > > On 11/7/18, Jesper Pedersen wrote:
> > > > Hi,
> > > >
> > > > While looking at [1] (included in 23315.log) there are other warnings as
> > > >
On 11/7/18 9:11 AM, Tomas Vondra wrote:
On 11/7/18 2:47 PM, John Naylor wrote:
On 11/7/18, Jesper Pedersen wrote:
Hi,
While looking at [1] (included in 23315.log) there are other warnings as
well.
Perhaps it's worth revisiting to make debugging easier, but right now
initdb.c has this
On 11/7/18 2:47 PM, John Naylor wrote:
> On 11/7/18, Jesper Pedersen wrote:
>> Hi,
>>
>> While looking at [1] (included in 23315.log) there are other warnings as
>> well.
>
> Perhaps it's worth revisiting to make debugging easier, but right now
> initdb.c has this comment:
>
> * Note:
> *
On 11/7/18, Jesper Pedersen wrote:
> Hi,
>
> While looking at [1] (included in 23315.log) there are other warnings as
> well.
Perhaps it's worth revisiting to make debugging easier, but right now
initdb.c has this comment:
* Note:
* The program has some memory leakage - it isn't worth
On 11/7/18 8:08 AM, Jesper Pedersen wrote:
While looking at [1] (included in 23315.log) there are other warnings as
well.
On 77366d90.
Best regards,
Jesper
Hi,
While looking at [1] (included in 23315.log) there are other warnings as
well.
I ran with
valgrind --leak-check=full --show-leak-kinds=all --gen-suppressions=all
--suppressions=/path/to/postgresql/src/tools/valgrind.supp
--time-stamp=yes --log-file=/tmp/valgrind/%p.log
