Обсуждение: PG Patch

This email is subject to a disclaimer which may be found on our website by clicking on this link: disclaimer. If you would prefer, the disclaimer can be emailed to you by clicking here.

On Tue, Mar 31, 2009 at 2:21 AM, Marc Abbott <MarcA@medscheme.co.za> wrote:

> Hi
>
> We have detected the following error in out PG logs:
>
> SASTERROR:  invalid memory alloc request size 4294967294.
>
> I have searched for the error and was pointed to a patch on the following
> link:
>
> http://anoncvs.postgresql.org/cvsweb.cgi/pgsql/src/backend/commands/vacuumlazy.c.diff?r1=1.61.2.1&r2=1.61.2.2
>
> Where can I find this patch and is there a specific way to apply the patch?
>
> Your help is appreciated.

That IS the patch.  However, why are you trying to patch pgsql by
hand?  Seems a hard way to do things.

What version of pgsql are you running and have  you tried just
updating to the latest release in your branch?

2009/3/31 Marc Abbott <MarcA@medscheme.co.za>:
> This email is subject to a disclaimer which may be found on our website by
> clicking on this link: disclaimer. If you would prefer, the disclaimer can
> be emailed to you by clicking here.
> Hi
> We have detected the following error in out PG logs:
> SASTERROR:  invalid memory alloc request size 4294967294.
> I have searched for the error and was pointed to a patch on the following
> link:
> http://anoncvs.postgresql.org/cvsweb.cgi/pgsql/src/backend/commands/vacuumlazy.c.diff?r1=1.61.2.1&r2=1.61.2.2
> Where can I find this patch and is there a specific way to apply the patch?

with the command patch -p0 if you have linux. You must create a mirror
of the directory
that contains the postgresql source.

> Your help is appreciated.
>
>
>
> Regards
>
> Marc



--
      Emanuel Calvo Franco
        Sumate al ARPUG !
      (www.postgres-arg.org -
         www.arpug.com.ar)
    ArPUG / AOSUG Member
   Postgresql Support & Admin

Scott Marlowe <scott.marlowe@gmail.com> writes:
> On Tue, Mar 31, 2009 at 2:21 AM, Marc Abbott <MarcA@medscheme.co.za> wrote:
>> http://anoncvs.postgresql.org/cvsweb.cgi/pgsql/src/backend/commands/vacuumlazy.c.diff?r1=1.61.2.1&r2=1.61.2.2

> That IS the patch.  However, why are you trying to patch pgsql by
> hand?  Seems a hard way to do things.
> What version of pgsql are you running and have  you tried just
> updating to the latest release in your branch?

That commit is three years old; if you are running a version that doesn't
include it, there is more than reason enough for an update.

            regards, tom lane