Is this fixed?
---
Tom Lane wrote:
Christopher Kings-Lynne [EMAIL PROTECTED] writes:
Maybe we could avoid removing it until the next checkpoint? Or is that
not enough. Maybe it could stay there forever :/
Part of
Bruce Momjian [EMAIL PROTECTED] writes:
Is this fixed?
Yes.
regards, tom lane
---(end of broadcast)---
TIP 9: the planner will ignore your desire to choose an index scan if your
joining column's datatypes do not
Added to open items:
* fix recovery of DROP TABLESPACE after checkpoint
---
Tom Lane wrote:
Christopher Kings-Lynne [EMAIL PROTECTED] writes:
Maybe we could avoid removing it until the next checkpoint? Or is
Did we resolve this?
---
Tom Lane wrote:
Christopher Kings-Lynne [EMAIL PROTECTED] writes:
Maybe we could avoid removing it until the next checkpoint? Or is that
not enough. Maybe it could stay there forever :/
Bruce Momjian [EMAIL PROTECTED] writes:
Did we resolve this?
No, it's an open issue.
regards, tom lane
---(end of broadcast)---
TIP 9: the planner will ignore your desire to choose an index scan if your
joining
Tom Lane wrote:
Christopher Kings-Lynne [EMAIL PROTECTED] writes:
Maybe we could avoid removing it until the next checkpoint? Or is that
not enough. Maybe it could stay there forever :/
Part of the problem here is that this code has to serve several
purposes. We have different
In CVS tip, try running the regression tests against an installed
postmaster (ie, make installcheck); then as soon as the tests are
done, kill -9 the bgwriter process to force a database restart.
Most of the time you'll get a PANIC during recovery:
LOG: background writer process (PID 2493) was
Tom Lane wrote:
In CVS tip, try running the regression tests against an installed
postmaster (ie, make installcheck); then as soon as the tests are
done, kill -9 the bgwriter process to force a database restart.
Most of the time you'll get a PANIC during recovery:
[...]
This is impossible
Gavin Sherry [EMAIL PROTECTED] writes:
On Wed, 4 Aug 2004, Tom Lane wrote:
Not really. If the replay code encounters an update to a table file
that's not there, it simply creates the file and plows ahead. The thing
that I'm stuck on about tablespaces is that if the symlink in
On Wed, 4 Aug 2004, Tom Lane wrote:
Kevin Brown [EMAIL PROTECTED] writes:
Tom Lane wrote:
This is impossible to fix nicely because the information to reconstruct
the tablespace is simply not available. We could make an ordinary
directory (not a symlink) under pg_tblspc and then limp
On Wed, 4 Aug 2004, Tom Lane wrote:
Gavin Sherry [EMAIL PROTECTED] writes:
On Wed, 4 Aug 2004, Tom Lane wrote:
Not really. If the replay code encounters an update to a table file
that's not there, it simply creates the file and plows ahead. The thing
that I'm stuck on about tablespaces
We do need to do that, but it will *not* solve this problem. The
scenario that causes the problem is
CREATE TABLESPACE
...
much time passes
...
CHECKPOINT
...
modify tables in tablespace
drop tables in tablespace
DROP
Tom Lane said:
The
scenario that causes the problem is
CREATE TABLESPACE
...
much time passes
...
CHECKPOINT
...
modify tables in tablespace
drop tables in tablespace
DROP TABLESPACE
...
system crash
Now the system
Gavin Sherry [EMAIL PROTECTED] writes:
CREATE TABLESPACE
...
much time passes
...
CHECKPOINT
...
modify tables in tablespace
drop tables in tablespace
DROP TABLESPACE
...
system crash
What happens here if no table spaces are
Bruce Momjian [EMAIL PROTECTED] writes:
Uh, why is the symlink not going to be there already?
Because we removed it at the DROP TABLESPACE.
regards, tom lane
---(end of broadcast)---
TIP 7: don't forget to increase your
Uh, why is the symlink not going to be there already?
Because we removed it at the DROP TABLESPACE.
Maybe we could avoid removing it until the next checkpoint? Or is that
not enough. Maybe it could stay there forever :/
Chris
---(end of
Christopher Kings-Lynne [EMAIL PROTECTED] writes:
Maybe we could avoid removing it until the next checkpoint? Or is that
not enough. Maybe it could stay there forever :/
Part of the problem here is that this code has to serve several
purposes. We have different scenarios to worry about:
17 matches
Mail list logo
