[postgis-devel] [pgrouting] need help with std::bad_alloc issue

[Sandro Santilli]

On Wed, Jun 12, 2013 at 02:40:01PM -0400, Stephen Woodbridge wrote:

> So I go back to the simplest case that I can run to reproduce this:
> 
> 1. createdb
> 2. connect and create postgis and pgrouting extensions
> 3. create a simple small table
> 4. run the query, get the error
> 5. \c to reconnect in psql
> 6. run same query it works
> 
> So new database, new connection, minimal work in session. Nothing
> that is requesting a huge amount of memory. This happens
> consistently regardless of server load or if I restart postgresql.
> 
> A slight variation in the above sequence:
> 
> 1. createdb
> 2. connect and create postgis and pgrouting extensions
> 3. \c to reconnect in psql
> 4. create a simple small table
> 5. run the query, get NO error

Can you look at memory usage right after the
"create pgrouting extension" step ?

> I found some code that I can call that will tell me the status of
> system memory usage, that I think I will add to the catch block and
> see if I can see what that is reporting. I have run this problem
> against valgrind without getting anything useful. And I have added
> debug output to trace down the specific line generating the error
> and that was not illuminating.

I'm happy to try the sequence above too, if you provide a
self-contained test. May help at least figuring out if it happens
on different systems.

> I hate problems like this.

I know your feeling

--strk;