s could be
changed to use SET LOCAL enable_mergejoin=off. That way, the setting
reverts to its original value automatically at the end of the
transaction. It seems more appropriate when using transaction mode
anyway.
--
Álvaro Herrera 48°01'N 7°57'E — https://www.EnterpriseDB.com/
ada1715-8208-4212-b352-d9ad2a1de...@thebuild.com
> It would help to also bring this up on:
>
> https://www.postgresql.org/list/pgsql-www/
Yeah.
--
Álvaro HerreraBreisgau, Deutschland — https://www.EnterpriseDB.com/
"I'm always right, but sometimes I'm more righ
Don't use these names in new code.
*/
#define CASHOID MONEYOID
#define LSNOID PG_LSNOID
/*
* End of backwards compatibility section.
*/
#define BOOLOID 16
#define BYTEAOID 17
--
Álvaro HerreraBreisgau, Deutschland — https://www.EnterpriseDB.com/
"I must say, I am
all accesses to the table.
Does your instance run with autovacuum disabled perchance?
--
Álvaro Herrera PostgreSQL Developer — https://www.EnterpriseDB.com/
Bob [Floyd] used to say that he was planning to get a Ph.D. by the "green
stamp method," namely by saving envelopes add
ttps://salsa.debian.org/postgresql/postgresql-common
--
Álvaro Herrera PostgreSQL Developer — https://www.EnterpriseDB.com/
"The Postgresql hackers have what I call a "NASA space shot" mentality.
Quite refreshing in a world of "weekend drag racer" developers."
(Scott Marlowe)
Maybe have a look at whether pg_wait_sampling can give you more clues.
Some basic bloat monitoring is a prerequisite to any further performance
tweaking anyhow.
--
Álvaro HerreraBreisgau, Deutschland — https://www.EnterpriseDB.com/
Maybe there's lots of data loss but the records o