On Thu, 20 Mar 2025, Dimitrios Apostolou wrote:
Rationale:
When restoring a backup in an emergency situation, it's fine to run
pg_restore as superuser and get an exact replica of the dumped db.
AFAICT pg_restore (without --data-only) is optimised for such case.
But pg_dump/restore can be used
On Fri, Mar 21, 2025 at 2:36 PM Dimitrios Apostolou wrote:
> On Thu, 20 Mar 2025, Dimitrios Apostolou wrote:
>
> > Rationale:
> >
> > When restoring a backup in an emergency situation, it's fine to run
> > pg_restore as superuser and get an exact replica of the dumped db.
>
How often do you have
> On Mar 19, 2025, at 07:47, Sebastien Flaesch
> wrote:
>
> Is there a plan to get pgvector's types (vector, halfvec, sparsevec, bit)
> implemented as native built-in data types like json/jsonb ?
(I'm speaking just for myself here.) I would not base any plans on this
functionality being a
Thank you everyone!
On Fri, Mar 21, 2025 at 7:23 PM Guillaume Lelarge <
guillaume.lela...@dalibo.com> wrote:
> On 20/03/2025 15:04, Adrian Klaver wrote:
> > On 3/20/25 05:58, Siraj G wrote:
> >> Hello Laurenz
> >>
> >> As per my understanding coming to a proper conclusion wrt RPO
> >
> > You stil
I have a list-partitioned table. When I query the base table but filter
by the partition column in a regular SQL query this takes a lock only on
the one partition being queried, as I expect. However, when the exact
same SQL query is run fom a DB function, with the partition ID passed in
as argument
On 20/03/2025 15:04, Adrian Klaver wrote:
On 3/20/25 05:58, Siraj G wrote:
Hello Laurenz
As per my understanding coming to a proper conclusion wrt RPO
You still have not defined what RPO is.
I guess the OP is talking about Recovery Point Objective, which is one
of two important parameter
