Re: Vacuuming leaked temp tables (once again)
От | Dave Page |
---|---|
Тема | Re: Vacuuming leaked temp tables (once again) |
Дата | |
Msg-id | 937d27e10807120156k21d02e31o4e7c41199e5129f5@mail.gmail.com обсуждение исходный текст |
Ответ на | Re: Vacuuming leaked temp tables (once again) (Simon Riggs <simon@2ndquadrant.com>) |
Ответы |
Re: Vacuuming leaked temp tables (once again)
|
Список | pgsql-hackers |
On Sat, Jul 12, 2008 at 9:16 AM, Simon Riggs <simon@2ndquadrant.com> wrote: > > So are you saying > > a) that other sessions need to be able to see pg_class entries for > temporary tables created by different sessions? > > b) that you need to be able to see pg_class entries for temporary tables > created only in your session? > > Hopefully you just mean (b)?? Not necessarily - it may be useful for an admin to peek at what tables are created by other sessions. I don't feel strongly about that though, moreso b). > The SQL Standard Information Schema does show LOCAL TEMPORARY and GLOBAL > TEMPORARY tables. Our implementation of temp tables differs from the > standard, so I think (b) is fully in line with that. My point is that any good admin tool will use pg_class directly, as information_schema doesn't include any of the Postgres specifc info that such a tool would want. FYI, pgAdmin doesn't do anything with temp tables at the moment anyway - I'm thinking of other apps that may do. An inheritance schema for pg_class may well work for them. -- Dave Page EnterpriseDB UK: http://www.enterprisedb.com
В списке pgsql-hackers по дате отправления: