| From: | Maxim Orlov <orlovmg(at)gmail(dot)com> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | pgsql-hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Do not lock temp relations |
| Date: | 2024-10-03 12:09:08 |
| Message-ID: | CACG=ezbFKGr-XDVe8X-OMAr6d0YsQHtx0t3h4v2-23cmpc6_qw@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Mon, 30 Sept 2024 at 18:05, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> Yes. Our implementation restrictions preclude access to the contents
> of another session's temp tables, but it is not forbidden to do DDL
> on them so long as no content access is required. (Without this,
> it'd be problematic for example to clean out a crashed session's temp
> tables. See the "orphan temporary tables" logic in autovacuum.c.)
>
OK, now I've realized the problem. Thanks a lot!
--
Best regards,
Maxim Orlov.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Robert Haas | 2024-10-03 12:34:31 | Re: pg_verifybackup: TAR format backup verification |
| Previous Message | Peter Eisentraut | 2024-10-03 11:31:19 | Re: Rename PageData to XLogPageData |