Nikolay SamokhvalovHost
Fabrízio MelloGuest
Michael ChristofidesHostSo, PG StatLog, do you want to give us a little bit of what it is and why you started work on it?

Well, PG StatLog is, say, it's the Postgres extension that solves, actually, at least tries to solve a very tricky problem on Postgres observability that is collect information about your logs in several different ways.

For example, your application is erroring out for some reason and you need to check what the error is happening after some deploy or something.

You need to go search the logs, grab the logs, and depending on where your post is running, it can be even tricky, right? Because you have managed service containers and all of different environments running postless.

So you can have a bunch of different ways to go to the logs and look for some.

It's a pgstat view inside Postgres that you collect counters, collect information about what is happening in your log.


And you can configure pgStatsLog to collect different error levels, depending on how much information you want to practice those content.

Instead of you go to jump into weird tools to access log, you have all the information you need, at least the basic information, inside your Postgres.

And for example, see over the time, it will rate you based on a specific application, for example.
So, PG StatLog, do you want to give us a little bit of what it is and why you started work on it?

Well, PG StatLog is, say, it's the Postgres extension that solves, actually, at least tries to solve a very tricky problem on Postgres observability that is collect information about your logs in several different ways.

For example, your application is erroring out for some reason and you need to check what the error is happening after some deploy or something.

You need to go search the logs, grab the logs, and depending on where your post is running, it can be even tricky, right? Because you have managed service containers and all of different environments running postless.

So you can have a bunch of different ways to go to the logs and look for some.

It's a pgstat view inside Postgres that you collect counters, collect information about what is happening in your log.


And you can configure pgStatsLog to collect different error levels, depending on how much information you want to practice those content.

Instead of you go to jump into weird tools to access log, you have all the information you need, at least the basic information, inside your Postgres.

And for example, see over the time, it will rate you based on a specific application, for example.
The rest of this transcript — segmented and speaker-labeled, so you land on the exact moment something was said
Search every transcript — by keyword, by phrase, or by meaning, across every show Radar indexes
Trends — what is surging across podcasts, measured against its own baseline
Alerts — when a name you follow appears in a newly indexed episode
No account is needed to search Radar.