PostgreSQL
`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.
Reminder: the Call for Papers for PGConf New York 2023 ends on Monday! Get your submissions in. #PostgreSQL #Conference #CfP #PGConfNYC
That's today! 16:00 UTC Let's talk about your unfinished proposal for #pgconfnyc, and polish it up so you can submit it! The CfP ends June 12th #PostgreSQL #CfP #Conference #NewYork