On 5/10/2010 10:02 AM, Tom Lane wrote:
Craig Ringer writes:
After turning autovacuum off completely, though, it does crash when
ANALYZE is run.
postgres.exe!pfree(void * pointer=0x68f08610) Line 591 + 0x3 bytes C
postgres.exe!examine_attribute(RelationData * onerel=0x, int attnu
Craig Ringer writes:
> After turning autovacuum off completely, though, it does crash when
> ANALYZE is run.
>> postgres.exe!pfree(void * pointer=0x68f08610) Line 591 + 0x3 bytes C
>> postgres.exe!examine_attribute(RelationData * onerel=0x, int
>> attnum=5, Node * index_expr=0x000
On 4/10/2010 10:56 AM, Tom Lane wrote:
Craig Ringer writes:
While it's consistently crashing my Pg 9 on win7 32-bit, too, I haven't
been able to get a backtrace yet. I thought it'd be trivial given the
ease of reproducing the crash - but the process that's crashing isn't
the backend running the
Robert Haas writes:
> On Mon, Sep 27, 2010 at 5:09 PM, Daniel Grace wrote:
>> Is there any chance this might be looked at in a future release?
> This is another interesting example of a case where an inlining-type
> optimization (which is effectively what's happening here, I think)
> turns out t
On Sun, Oct 3, 2010 at 12:16 PM, Tony marston
wrote:
>
> The following bug has been logged online:
>
> Bug reference: 5690
> Logged by: Tony marston
> Email address: t...@marston-home.demon.co.uk
> PostgreSQL version: 9.0
> Operating system: Windows XP
> Description: pg
On Wed, Sep 29, 2010 at 2:20 PM, Nathan Gorter wrote:
> I am attempting to perform a dump from one database, create a new database,
> and restore the data to that new database. In my old database I have schemas
> besides the public schema that I have created myself. The pg_dump works fine
> and th
On Mon, Oct 4, 2010 at 4:15 PM, Daniel Grace wrote:
> As a theoretical question (I'm not savvy on Postgres's code but might
> be intrigued enough to beat on it anyways), is it feasible to do an
> additional pass on the query plan that essentially goes:
>
> - Are these two subplans identical?
> - A
As a theoretical question (I'm not savvy on Postgres's code but might
be intrigued enough to beat on it anyways), is it feasible to do an
additional pass on the query plan that essentially goes:
- Are these two subplans identical?
- Are they at the same part of the tree?
and if both of these cond
On Mon, Oct 4, 2010 at 11:59, V.J. wrote:
> * Starting PostgreSQL 8.4 database server
> * The PostgreSQL server failed to start. Please check
> the log output:
> 2010-10-04 19:58:40 CEST FATAL: konnte auf private Schl?sseldatei
>>>server.key<< nicht zugreifen: No such file o
The following bug has been logged online:
Bug reference: 5692
Logged by: V.J.
Email address: molo...@gmx.de
PostgreSQL version: 8.4
Operating system: Ubuntu Lucid 10.04
Description:fatal error
Details:
* Starting PostgreSQL 8.4 database server
On Mon, Sep 27, 2010 at 5:09 PM, Daniel Grace wrote:
> Is there any chance this might be looked at in a future release?
This is another interesting example of a case where an inlining-type
optimization (which is effectively what's happening here, I think)
turns out to be a negative. We had one a
Hi,
I have do some other test.
I set
autovacuum = off.
With this setting the server don't crash.
But certainly something go bad.
Infact
if (after run the query) I connect with posql as user 'postgres' and try
a single command
VACUUM;
nothing happened.
But if I try a
single command
ANALYZE;
Just an update on this issue:
I've been able to reproduce the crash (thanks for the test case!) and
obtain the crash information here on my 32-bit windows 7 install, so
there's no need for you to do anything else so far.
I still can't get a usable backtrace. The autovacuum workers/launcher
sp
The following bug has been logged online:
Bug reference: 5691
Logged by: Tatsuhito Kasahara
Email address: kasahara.tatsuh...@oss.ntt.co.jp
PostgreSQL version: 9.0
Operating system: Any
Description:Documentation typo ?
Details:
The following is a part of doc/src/sgm
14 matches
Mail list logo
