Why is my WAL directory so large?
Why is my WAL directory so large? – select * from depesz;
https://www.depesz.com/2023/06/18/why-is-my-wal-directory-so-large/
Lemmy PostgreSQL - can someone please help deconstruct this INSERT SQL: INSERT INTO "comment_like"...
INSERT INTO "comment_like" ("person_id", "comment_id", "post_id", "score") VALUES ($1, $2, $3, $4) ON CONFLICT ("comment_id", "person_id") DO UPDATE SET "person_id" = $5, "comment_id" = $6, "post_id" = $7, "score" = $8 RETURNING "comment_like"."id", "comment_like"."person_id", "comment_like"."comment_id", "comment_like"."post_id", "comment_like"."score", "comment_like"."published"
The server is showing relatively high execution time for this INSERT statement, like 0.4 seconds mean time. Is this form of blended INSERT with UPDATE and RETURNING slower than doing a direct insert? (was misreading data, these are milliseconds, not seconds)
Every time a remote federation Upvote on a comment comes in to Lemmy, it executes this statement.
PostgreSQL reconsiders its process-based model [LWN.net]
PostgreSQL reconsiders its process-based model [LWN.net]
https://lwn.net/SubscriberLink/934940/3abb2d4086680b78/
PostgreSQL Person of the Week interview with: Sharan Foga
Interview with: Sharan Foga | PostgreSQL Person of the Week
https://postgresql.life/post/sharan_foga/
PostgreSQL Person of the Week interview with Sharan Foga, published 05.06.2023, interview conducted by Andreas Scherbaum
PGConf New York Talk Submissions
Andreas Scherbaum (@ascherbaum@mastodon.social)
https://mastodon.social/@ascherbaum/110469842048716169
What about this proposal idea you have for PGConf NYC, but not sure how to submit it? Let's talk about your proposal, next Monday, June 5th, 16:00 UTC. Members from the #PostgreSQL community can help you landing your talk in the submission queue! #pgconfnyc #conference #CfP https://adjust.zoom.us/j/97076935026?pwd=aUdUVUFZbXVmeTR1QWdMK2ZpemhHZz09
PostgreSQL and SQL:2023
PostgreSQL and SQL:2023
http://peter.eisentraut.org/blog/2023/04/18/postgresql-and-sql-2023
In a previous article, I introduced what is new in SQL:2023. Now I want to show the status of SQL:2023 support in PostgreSQL. See the previous article for details on these features.