On Wed, 28 Aug 2024 at 18:59, Justin Clift wrote:
> Any idea who normally does those, and if it would be reasonable to add
> test(s) for the internal information tables?
These tend to get added along with features and along with of bug
fixes. I imagine any tests for the information_schema views
List,
I am doing a full backup using PgBackRest from a production server to
Reposerver.
My connection is IPSec VPN over ILL ( 8 Mbps link) between the
Production DB Server and the remote RepoServer.
I understood the bottleneck of 8 Mbps between servers. (Server NICs 10Gbps
and switch)
Que
Thank you all for the great help ..
I couldn't get a chance toRestart the DB Cluster after making the
changes highlighted. Correct me if I am wrong ( production server, down
time requested. ) after editing the pg_hba.conf on DB server as
follows
local all all
List,
I am configuring the Pgbackrest ( RHEL9.4 , EPAS 16 , PgbackRest
2.52.1 ) on two servers.(Database cluster server and Repo Server).
Query.1 Do I need to create stanza on both servers ( DB server EPAS16
User : enterprisedb,as well as on RepoServer user: postgres )
1.
>
> Any value in supplying a single insert statement a la (less back and forth
> perhaps?):
>
Yes, absolutely that would be better. This particular endpoint has some
ancient + crufty code backing it (migrated from a NoSQL DB with a
db-agnostic shim that we're slowly replacing). The old code likes
> On Aug 28, 2024, at 10:18 AM, Jacob Biesinger
> wrote:
>
> But to go deeper, we use the javascript knex adapter and some
> application-level transaction management that automatically retries a
> transaction N times when it encounters serialization errors. On this
> particular endpoint, th
On Wed, Aug 28, 2024 at 5:39 AM Greg Sabino Mullane
wrote:
> On Tue, Aug 27, 2024 at 9:03 PM Jacob Biesinger
> wrote:
>
>> I'm scratching my head at a few rows in the root DB, where it seems the
>> corresponding tenant transaction rolled back, but the root DB transaction
>> committed
>>
> ...
>
On Wednesday, August 28, 2024, Amitabh Kant wrote:
> On Wed, Aug 28, 2024 at 8:00 PM David G. Johnston <
> david.g.johns...@gmail.com> wrote:
>
>> On Wednesday, August 28, 2024, KK CHN wrote:
>>
>>>
>>> and I have .pgpass in DB server as
>>>
>>
>> You assumed this mattered but I see no mention
On Wed, Aug 28, 2024 at 8:00 PM David G. Johnston <
david.g.johns...@gmail.com> wrote:
> On Wednesday, August 28, 2024, KK CHN wrote:
>
>>
>> and I have .pgpass in DB server as
>>
>
> You assumed this mattered but I see no mention that pgBackRest consults
> this file.
>
> It seems to require th
On Wednesday, August 28, 2024, KK CHN wrote:
>
> and I have .pgpass in DB server as
>
You assumed this mattered but I see no mention that pgBackRest consults
this file.
It seems to require the local entry in pg_hba.conf to use peer
authentication.
David J.
I am trying pgbackrest config on a Production Server and a Repo server (
RHEL 9.4 EPAS 16 , pgbackrest 2.52.1
I have configured pbbackrest.conf on both machines as per the official
docs.
>From b*oth machines password less auth works for the db user *(enterprisedb
) and repouser(postgres)
.
Very helpful.
On Wed, Aug 28, 2024 at 5:51 PM Greg Sabino Mullane
wrote:
> On Wed, Aug 28, 2024 at 1:39 AM KK CHN wrote:
>
>> In this DB serverI have other databases than the default "edb"
>> database. Specifying the above line aspg1-database=edb // I am
>> not sure this line is
On Tue, Aug 27, 2024 at 9:03 PM Jacob Biesinger
wrote:
> I'm scratching my head at a few rows in the root DB, where it seems the
> corresponding tenant transaction rolled back, but the root DB transaction
> committed
>
...
> Before I jump into particulars, does this sound like expected behavior?
On Wed, Aug 28, 2024 at 1:39 AM KK CHN wrote:
> In this DB serverI have other databases than the default "edb"
> database. Specifying the above line aspg1-database=edb // I am
> not sure this line is necessary or not ?
>
The pgbackrest process needs to connect to the database, w
On Tue, 2024-08-27 at 19:29 +0200, Jean-Christophe Boggio wrote:
> I have 2 very confusing behaviors when using ranges.
>
> It all started with this query:
>
> WITH rangespaliers AS (
> SELECT numrange( qtep1+1 , qtep2, '[]') AS rangep FROM
> paliers JOIN tmp_limitcontrats USING
15 matches
Mail list logo
