| From: | Jim Finnerty <jfinnert(at)amazon(dot)com> |
|---|---|
| To: | pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: Feature improvement: can we add queryId for pg_catalog.pg_stat_activity view? |
| Date: | 2019-03-19 17:23:55 |
| Message-ID: | 1553016235129-0.post@n3.nabble.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
The queryId depends on oids, so it is not stable enough for some purposes.
For example, to create a SQL identifier that survives across a server
upgrade, or that can be shipped to another database, the queryId isn't
usable.
The apg_plan_mgmt extensions keeps both its own stable SQL identifier as
well as the queryId, so it can be used to join to pg_stat_statements if
desired. If we were to standardize on one SQL identifier, it should be
stable enough to survive a major version upgrade or to be the same in
different databases.
-----
Jim Finnerty, AWS, Amazon Aurora PostgreSQL
--
Sent from: http://www.postgresql-archive.org/PostgreSQL-hackers-f1928748.html
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Andres Freund | 2019-03-19 17:24:41 | Re: Willing to fix a PQexec() in libpq module |
| Previous Message | Tom Lane | 2019-03-19 17:18:25 | Re: Willing to fix a PQexec() in libpq module |