| From: | Celia McInnis <celia(dot)mcinnis(at)gmail(dot)com> |
|---|---|
| To: | Thomas Munro <thomas(dot)munro(at)gmail(dot)com> |
| Cc: | pgsql-general <pgsql-general(at)postgresql(dot)org> |
| Subject: | Re: spiexceptions.UndefinedFile: could not open file "base/16482/681830": No such file or directory |
| Date: | 2021-09-09 03:55:20 |
| Message-ID: | CAGD6t7L0sMMzaZgx1a0zp+ZA60GjG6Qufa3wu=zKLp2V-9T5QA@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
YES!!! The chdir caused the error! Thanks very much for this help. BTW it
was worse than just "not a very good idea" to use chdir - After generating
the error, I would lose the ability to see things in my database until
restarting postgresql. All's okay now!
On Wed, Sep 8, 2021 at 8:56 PM Thomas Munro <thomas(dot)munro(at)gmail(dot)com> wrote:
> On Thu, Sep 9, 2021 at 9:19 AM Celia McInnis <celia(dot)mcinnis(at)gmail(dot)com>
> wrote:
> > Note that the file does exist:! (How do I know if it is looking under
> the correct directory? Other times I have done similar temporary table
> creations with no problems!):
>
> PostgreSQL internally uses relative paths. It's probably not a very
> good idea to use 'chdir' in a procedure.
>
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Abhishek Bhola | 2021-09-09 05:52:25 | Postgresql 11: terminating walsender process due to replication timeout |
| Previous Message | Thomas Munro | 2021-09-09 00:56:13 | Re: spiexceptions.UndefinedFile: could not open file "base/16482/681830": No such file or directory |