Skip site navigation (1) Skip section navigation (2)

Re: BUG #3232: Regression: pgsql server startup problem with encrypted partitions

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: "Carsten" <fcarsten(at)tpg(dot)com(dot)au>
Cc: pgsql-bugs(at)postgresql(dot)org
Subject: Re: BUG #3232: Regression: pgsql server startup problem with encrypted partitions
Date: 2007-04-18 05:28:05
Message-ID: 20990.1176874085@sss.pgh.pa.us (view raw or flat)
Thread:
Lists: pgsql-bugs
"Carsten" <fcarsten(at)tpg(dot)com(dot)au> writes:
> Were there any changes which made the pgsql server stricter in requiring
> that all table-spaces exist on start-up?

Not that I can think of --- except that startup for crash recovery has
always expected everything to be accessible.  If that's not what you're
running into, please provide a full test case.

			regards, tom lane

In response to

pgsql-bugs by date

Next:From: Magnus HaganderDate: 2007-04-18 07:36:18
Subject: Re: BUG #3232: Regression: pgsql server startup problem with encrypted partitions
Previous:From: Tom LaneDate: 2007-04-18 05:24:46
Subject: Re: BUG #3235: Partitioning has problem with timestamp and timestamptz data types

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group