pg.ddx.io  pgsql-admin@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Tom Lane <tgl@sss.pgh.pa.us>
To: Robert Voinea <robert.voinea@topex.ro>
Cc: pgsql-admin@postgresql.org
Subject: Re: Server crash when using dblink_build_sql_* after alter table
Date: Mon, 14 Jun 2010 13:36:27 -0400
Message-ID: <15794.1276536987@sss.pgh.pa.us> (raw)
In-Reply-To: <201006141415.09471.robert.voinea@topex.ro>
References: <201006111551.23382.robert.voinea@topex.ro>
	<7091.1276266088@sss.pgh.pa.us>
	<201006141415.09471.robert.voinea@topex.ro>

Robert Voinea <robert.voinea@topex.ro> writes:
> I attached the server log (for the crash case) and a test case with logs.
> For that test case this is the error I get, no server crash.

> ERROR:  invalid memory alloc request size 4294967293

> The scenario is this:
> Create a table, drop a column, any column then add a varchar column and an int 
> column. Then use dblink_build_sql_update.

Yeah, it looks like dblink is simply wrong about how to count the
columns in a case with dropped columns.  Thanks for the report, will
fix.

			regards, tom lane



view thread (6+ messages)  latest in thread

Message-ID: <15794.1276536987@sss.pgh.pa.us>
Permalink:  ../15794.1276536987@sss.pgh.pa.us/
Also on:    postgresql.org/message-id/15794.1276536987@sss.pgh.pa.us

 · 

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: pgsql-admin@postgresql.org
  Cc: tgl@sss.pgh.pa.us, robert.voinea@topex.ro
  Subject: Re: Server crash when using dblink_build_sql_* after alter table
  In-Reply-To: <15794.1276536987@sss.pgh.pa.us>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox