On Mon, May 16, 2011 at 8:04 AM, Pascal Borschneck <borschn...@hotmail.com>wrote:
> Hi Robert, > > Sorry for the late reply, I was not here last week. > > About your question: "*That's kind of surprising, but I can't help > wondering if it's a bug in what virtualization tool you are using.*" > I noticed the problem FIRST on VM. And by pausing/stopping/launching a VM > it was easy to get these error back. > > *But since some weeks*, I also had duplicates on real server. And same > result if I try to launch a VACUUM: crash with the same assertion. > Which "*stack trace on the assertion failure*" do you want to have ? > Well, when a backend crashes, it would be helpful to know what was going on when it crashed. See this wiki page: http://wiki.postgresql.org/wiki/Generating_a_stack_trace_of_a_PostgreSQL_backend -- Robert Haas EnterpriseDB: http://www.enterprisedb.com The Enterprise PostgreSQL Company
