Re: PostgresNode::_update_pid using undefined variables in tap tests

From: Michael Paquier <michael(dot)paquier(at)gmail(dot)com>
To: Robert Haas <robertmhaas(at)gmail(dot)com>
Cc: PostgreSQL mailing lists <pgsql-hackers(at)postgresql(dot)org>, Alvaro Herrera <alvherre(at)2ndquadrant(dot)com>
Subject: Re: PostgresNode::_update_pid using undefined variables in tap tests
Date: 2015-12-08 23:09:30
Message-ID: CAB7nPqQOx-irB9OOr=ejFzxd-VXYdJxsF-yO+LAu5uGhrvJp3Q@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Wed, Dec 9, 2015 at 4:47 AM, Robert Haas <robertmhaas(at)gmail(dot)com> wrote:
>
> On Thu, Dec 3, 2015 at 11:28 PM, Michael Paquier
> <michael(dot)paquier(at)gmail(dot)com> wrote:
> > This does not impact the run, but it creates unwelcome warnings in the
> > logs. This is actually caused by the following code in PostgresNode
> > that uses an incorrect check to see if the file has been correctly
> > opened or not:
> > open my $pidfile, $self->data_dir . "/postmaster.pid";
> > if (not defined $pidfile)
> >
> > One way to fix this is to use if(open(...)), a second way I know of is
> > to check if the opened file handle matches tell($pidfile) == -1. The
> > patch attached uses the first method to fix the issue.
>
> My Perl-fu must be getting weak. What's wrong with the existing code?

This code should have checked for the return result of open instead of
looking at $pidfile. This has been noticed by Noah as well afterwards
and already addressed as 9821492.
--
Michael

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Jim Nasby 2015-12-08 23:39:35 Re: Fwd: Another little thing about psql wrapped expanded output
Previous Message Robert Haas 2015-12-08 22:30:33 Re: Patch: ResourceOwner optimization for tables with many partitions