Nikolay SamokhvalovHost
Michael ChristofidesHostAnd for the case of replication, the idea to build it, to have it in core one, for the case of autofillover, it lost.
I'm very curious what you think about the idea to have full-fledged backup solution inside core and why it's not happening.
One interesting historical fact is, and one of the reasons why some of the other committers were involved in really early planning, and part of the reason for the migration to C was the idea was that we could actually maybe make pgbackrest the core solution for backup.
broadly, or it was just discussions that I had with some committers, you know, because they were interested in having a more comprehensive solution in core.
As for actually having something like pgvacquers in core, it's a little tricky because the pgvacquers project moves a lot faster than core does.
So to have it on the yearly cycle would be, let's say we had put PG backrest and decor from the beginning, maybe as soon as it was migrated to C.
We went down to six, and now we're currently at four, which I think is just about the right tempo for a project of this type.
But being able to release features four times a year, get new stuff out there, get people trying it, get people testing it, that kind of stuff, I think it's pretty important.
Postgres, memcontext, and error handling looks a lot similar and et cetera, et cetera.
And for the case of replication, the idea to build it, to have it in core one, for the case of autofillover, it lost.
I'm very curious what you think about the idea to have full-fledged backup solution inside core and why it's not happening.
One interesting historical fact is, and one of the reasons why some of the other committers were involved in really early planning, and part of the reason for the migration to C was the idea was that we could actually maybe make pgbackrest the core solution for backup.
broadly, or it was just discussions that I had with some committers, you know, because they were interested in having a more comprehensive solution in core.
As for actually having something like pgvacquers in core, it's a little tricky because the pgvacquers project moves a lot faster than core does.
So to have it on the yearly cycle would be, let's say we had put PG backrest and decor from the beginning, maybe as soon as it was migrated to C.
We went down to six, and now we're currently at four, which I think is just about the right tempo for a project of this type.
But being able to release features four times a year, get new stuff out there, get people trying it, get people testing it, that kind of stuff, I think it's pretty important.
Postgres, memcontext, and error handling looks a lot similar and et cetera, et cetera.
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.