Re: [Dbdpg-general] 'prepare' is not quite schema-safe

From: Dana Hudes <dhudes(at)tcp-ip(dot)info>
To: Vlad <marchenko(at)gmail(dot)com>
Cc: pgsql-general(at)postgresql(dot)org, dbdpg-general(at)gborg(dot)postgresql(dot)org
Subject: Re: [Dbdpg-general] 'prepare' is not quite schema-safe
Date: 2005-05-02 01:55:58
Message-ID: Pine.LNX.4.58.0505012152320.28940@screamer.tcp-ip.info
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

On Sun, 1 May 2005, Vlad wrote:

> Hello,
>
> I'm seeking for an advise to solve the issue that we hit recently
> (cost me sleepless night after production server upgrade).

the first problem you have is that you have a critical production system
that you upgraded without going through proper test first.
That's just bad change control.
In any case, if the new DBD::Pg blew up in your face why did you not
immediately revert to the previous working one? Even if you didn't have it
on disk anymore you can just re-download it explicitly.
If it were no longer on CPAN it is on the 'backpan'.

Just because its Linux, or Postgresql or Perl, doesn't mean you don't have
to follow proper operational procedures.

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message CSN 2005-05-02 02:08:39 Re: could not load library plperl.so
Previous Message Tom Lane 2005-05-02 01:51:13 Re: could not load library plperl.so