Re: [PHP] [BUGS] PostgreSQL / PHP Overrun Error - Mailing list pgsql-hackers

From Bruce Momjian
Subject Re: [PHP] [BUGS] PostgreSQL / PHP Overrun Error
Date
Msg-id 200109281950.f8SJoCj14352@candle.pha.pa.us
Whole thread Raw
In response to Re: [PHP] [BUGS] PostgreSQL / PHP Overrun Error  ("Mike Rogers" <temp6453@hotmail.com>)
Responses Re: [PHP] [BUGS] PostgreSQL / PHP Overrun Error
List pgsql-hackers
> I'm using the current CVS (4.0.8-dev)- It's spectacular.  Lower memory
> usage, more descriptive debug, better control over it.  Tons more options,
> smaller code, much much faster.
>
>     Can you trust it- sure.  It isn't a release candidate.  It is the
> current development version.  As they find problems, they get fixed.  As
> long as you keep a bit on top you are fine.  If anything it is _MORE_ secure
> than the current version, as any security problems were fixed earlier as
> soon as they get found, and new bugs aren't known yet.  I'm seriously
> impressed with it and feel like I will be using the CVS code quite a bit
> more.  Any bugs Zend memory manager cleans up anyway.
>
>     Note: if you are not having the problem of 0 rows or buffer overruns,
> don't bother upgrading as it will not benefit you.  Clearly I was and the
> new code fixed the flaws in the existing code for my usage.

Keep in mind we can change the on-disk structure or system tasbles
anytime so you may have trouble moving between different CVS versions.

--
  Bruce Momjian                        |  http://candle.pha.pa.us
  pgman@candle.pha.pa.us               |  (610) 853-3000
  +  If your life is a hard drive,     |  830 Blythe Avenue
  +  Christ can be your backup.        |  Drexel Hill, Pennsylvania 19026

pgsql-hackers by date:

Previous
From: Bruce Momjian
Date:
Subject: Re: Fragmenting tables in postgres
Next
From: Bradley McLean
Date:
Subject: Plpython bug with int8?