| From: | Michael Paquier <michael(at)paquier(dot)xyz> |
|---|---|
| To: | Aayush Chaturvedi <chaturvedi98293(at)gmail(dot)com> |
| Cc: | pgsql-bugs(at)lists(dot)postgresql(dot)org |
| Subject: | Re: BUG #15905: FATAL: the database system is starting up |
| Date: | 2019-07-13 05:49:54 |
| Message-ID: | 20190713054954.GB2137@paquier.xyz |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
On Sat, Jul 13, 2019 at 12:15:12AM +0530, Aayush Chaturvedi wrote:
> So I created tablespaces on my local system and I think that what was
> coming in the logs.
db2dascmn64.dll is a DLL coming from some stuff of IBM's DB2. You may
want to check why you have executables in your data folder to begin
with. These are *not* part of the original data folder created by
initdb. So something in your installation is already not clear. If a
DLL is being accessed for a reason or another, a base backup will
logically fail on it if another process out of PostgreSQL's backend
use it. Postgres open() calls are shared-safe thanks to a custom
wrapper we have in the tree, but that's not the case of the native
implementation on Windows.
--
Michael
| From | Date | Subject | |
|---|---|---|---|
| Next Message | PG Bug reporting form | 2019-07-13 08:37:47 | BUG #15906: Insert ops within a branch of "RETURN QUERY WITH" are not seen by a subsequent SELECT |
| Previous Message | Manuel Rigger | 2019-07-12 23:18:53 | Re: ERROR: found unexpected null value in index |