public inbox for [email protected]help / color / mirror / Atom feed
Explain docs and the regression database 3+ messages / 3 participants [nested] [flat]
* Explain docs and the regression database @ 2010-05-30 02:33 Greg Smith <[email protected]> 0 siblings, 1 reply; 3+ messages in thread From: Greg Smith @ 2010-05-30 02:33 UTC (permalink / raw) To: pgsql-docs The introduction to using EXPLAIN: http://developer.postgresql.org/pgdocs/postgres/using-explain.html includes a footnote at the bottom suggesting you might follow along with these examples because they come from the regression test database. This would really be a lot more useful if it gave some sort of clue just how exactly a user might get that database populated with that regression data. I'm not even quite sure myself exactly what point in the regression testing cycle these examples came from. Another open question in my head is whether enough pieces of the regression set are shipped in the most common packaging sets that it's ever practical to expect users to run the tests at all. Thoughts? -- Greg Smith 2ndQuadrant US Baltimore, MD PostgreSQL Training, Services and Support [email protected] www.2ndQuadrant.us ^ permalink raw reply [nested|flat] 3+ messages in thread
* Re: Explain docs and the regression database @ 2010-05-30 03:37 Tom Lane <[email protected]> parent: Greg Smith <[email protected]> 0 siblings, 1 reply; 3+ messages in thread From: Tom Lane @ 2010-05-30 03:37 UTC (permalink / raw) To: Greg Smith <[email protected]>; +Cc: pgsql-docs Greg Smith <[email protected]> writes: > The introduction to using EXPLAIN: > http://developer.postgresql.org/pgdocs/postgres/using-explain.html > includes a footnote at the bottom suggesting you might follow along with > these examples because they come from the regression test database. > This would really be a lot more useful if it gave some sort of clue just > how exactly a user might get that database populated with that > regression data. You run the regression tests. > I'm not even quite sure myself exactly what point in > the regression testing cycle these examples came from. The ending state. > Another open > question in my head is whether enough pieces of the regression set are > shipped in the most common packaging sets that it's ever practical to > expect users to run the tests at all. Thoughts? In Fedora/RHEL, and I believe also the PGDG RPMs, you'd install the postgresql-test RPM and run it per directions. regards, tom lane ^ permalink raw reply [nested|flat] 3+ messages in thread
* Re: Explain docs and the regression database @ 2010-05-31 14:21 Bruce Momjian <[email protected]> parent: Tom Lane <[email protected]> 0 siblings, 0 replies; 3+ messages in thread From: Bruce Momjian @ 2010-05-31 14:21 UTC (permalink / raw) To: Tom Lane <[email protected]>; +Cc: Greg Smith <[email protected]>; pgsql-docs Tom Lane wrote: > Greg Smith <[email protected]> writes: > > The introduction to using EXPLAIN: > > http://developer.postgresql.org/pgdocs/postgres/using-explain.html > > includes a footnote at the bottom suggesting you might follow along with > > these examples because they come from the regression test database. > > This would really be a lot more useful if it gave some sort of clue just > > how exactly a user might get that database populated with that > > regression data. > > You run the regression tests. FYI, I think you have to run 'installcheck' so the database remains after the regression tests. -- Bruce Momjian <[email protected]> http://momjian.us EnterpriseDB http://enterprisedb.com ^ permalink raw reply [nested|flat] 3+ messages in thread
end of thread, other threads:[~2010-05-31 14:21 UTC | newest] Thread overview: 3+ messages (download: mbox mbox.gz follow: Atom feed) -- links below jump to the message on this page -- 2010-05-30 02:33 Explain docs and the regression database Greg Smith <[email protected]> 2010-05-30 03:37 ` Tom Lane <[email protected]> 2010-05-31 14:21 ` Bruce Momjian <[email protected]>
This inbox is served by agora; see mirroring instructions for how to clone and mirror all data and code used for this inbox