| From: | Qingqing Zhou <zhouqq(dot)postgres(at)gmail(dot)com> |
|---|---|
| To: | Jim Nasby <Jim(dot)Nasby(at)bluetreble(dot)com> |
| Cc: | Alvaro Herrera <alvherre(at)2ndquadrant(dot)com>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Tatsuo Ishii <ishii(at)postgresql(dot)org>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Planner debug views |
| Date: | 2015-07-31 18:55:24 |
| Message-ID: | CAJjS0u3Nez-Q_wSGhyMCLmqwDt6v0-Nze9B8HSGkaDZKNQKVrw@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Thu, Jul 30, 2015 at 2:42 PM, Jim Nasby <Jim(dot)Nasby(at)bluetreble(dot)com> wrote:
>
> I think a better option would be shoving it into a backend tuplestore and
> just leaving it there (maybe with a command to clear it for the paranoid).
> That gives a relation you can query against, insert into another table, etc.
> --
This is something I don't know how to do it: in my understanding, a
tuplestore is an internal store, which means it has no name exposed.
Thus we can't reference it later.
Regards,
Qingqing
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Robert Haas | 2015-07-31 19:00:49 | Re: 64-bit XIDs again |
| Previous Message | Robert Haas | 2015-07-31 18:54:39 | Re: [PROPOSAL] VACUUM Progress Checker. |