Collation Conundrum | Scaling Postgres 307

from Scaling Postgres · host Creston Jamison

In this episode of Scaling Postgres, we discuss whether we should be using bytewise or linguistic ordering by default, how to transform data in Postgres, benefits of a transaction_timeout and how to enforce join order. To get the show notes as well as get notified of new episodes, visit: https://www.scalingpostgres.com/episodes/307-collation-conundrum/

Episode metadata supplied by the publisher feed · Published Mar 17, 2024

Embed this episode

Attribution link and audio player

Ready to play

Collation Conundrum | Scaling Postgres 307

0:00 14:22

1×

No transcript for this episode yet

We transcribe on demand. Request one and we'll notify you when it's ready — usually under 10 minutes.

Share this episode

Similar Episodes

No similar episodes found.

Similar Podcasts

Agile Plays Agile Plays For the past decade I have been working with scaling technology organizations who need to address the challenges of how to scale revenue, customer base, and employee headcount."Agile Plays" (http://agileplays.co.uk) are a set of strategies for scalability. Like a successful sports team you compile a set of strategies or “Plays”. These give potential solutions and the team chooses Plays as appropriate to gain advantage.

Frequently Asked Questions

How long is this episode of Scaling Postgres?

This episode is 14 minutes long.

When was this Scaling Postgres episode published?

This episode was published on March 17, 2024.

Can I download this Scaling Postgres episode?

Yes. Use the download control on the episode player to save the publisher-provided media file.

URL copied to clipboard!