andby.
Yahoo Mail: Search, Organize, Conquer
On Thu, Sep 11, 2025 at 9:19 PM, Euler Taveira wrote: On
Thu, Sep 11, 2025, at 10:07 PM, Efrain J. Berdecia wrote:
> The error I would like to address with this feature is the following:
>
> FATAL: highest timeline xxx of the primary is be
known
Category: Include the text: Restore, replication
Thanks in advance Efrain J Berdecia
: On Thursday, September 11, 2025,
Efrain J. Berdecia wrote:
One-line Summary: This new recovery_target_timeline option would ensure that
when rebuilding a replica cluster, the recovery stays in the primary cluster's
timeline making it fool proof and avoiding recovery timeline inconsistencies.
Mail: Search, Organize, Conquer
On Thu, Sep 11, 2025 at 8:50 PM, Euler Taveira wrote: On
Thu, Sep 11, 2025, at 9:17 PM, Efrain J. Berdecia wrote:
> *One-line Summary:* This new recovery_target_timeline option would
> ensure that when rebuilding a replica cluster, the recovery stay
J. Berdecia wrote:
> *One-line Summary:* This new recovery_target_timeline option would
> ensure that when rebuilding a replica cluster, the recovery stays in
> the primary cluster's timeline making it fool proof and avoiding
> recovery timeline inconsistencies.
>
Do you
migration dba team determined citext was the way to go to
maintain MSSQL existing usage of the data in the columns.
Thanks,Efrain J. Berdecia
On Thursday, January 13, 2022, 10:10:38 AM EST, Tom Lane
wrote:
"Efrain J. Berdecia" writes:
> In our setup it has actually worked per
Thank you for the feedback.
In our setup it has actually worked per the explains provided making the query
run in milliseconds instead of seconds.
We weren't sure if this should be something that could be added natively with
future Postgres deployments.
Thanks,Efrain J. Berdecia
After attempting to use gin and gist indexes for our queries that run against
citext columns, our team has come up with the following to make our queries run
from 2 mins to 25ms;CREATE EXTENSION pg_trgmCREATE EXTENSION btree_gin --may
not be needed, checking
CREATE OPERATOR CLASS gin_trgm_ops_ci
Are there any plans to add a create and last updated time stamp field to any
and all objects in postgres?
Possibly even adding a updated_by documenting which role created and last
updated the object.
All done natively and without the need for extra extensions.
Thanks in advance.
