On Fri, Mar 29, 2024 at 4:47 AM Nick Renders wrote:
> Looking at the 2 machines that are having this issue (and the others that
> don't), I think it is somehow related to the following setup:
> - macOS Sonoma (14.4 and 14.4.1)
> - data directory on an external drive
>
> That external drive (a
On 2024-03-28 22:43 +0100, sud wrote:
> Regarding my second question, I am still unable to find out why we are
> seeing "*no privileges were granted for cron/partman/part_config*' message
> while adding the grants to the user?
Because the role that is granting the privileges is missing the grant
On Thu, 2024-03-28 at 17:17 +0100, Emond Papegaaij wrote:
> Op do 28 mrt 2024 om 16:21 schreef Laurenz Albe :
> > On Thu, 2024-03-28 at 15:52 +0100, Emond Papegaaij wrote:
> > > pg_rewind: source and target cluster are on the same timeline pg_rewind:
> > > no rewind required
> > >
> > > If we
On Thu, Mar 28, 2024 at 5:28 PM Lok P wrote:
> Hello All,
> In RDS postgres(version 15.4), we have scheduled partition maintenance
> through pg_partman and it's scheduled through pg_cron as below. The same
> script has been executed in dev and test environments, and we are seeing
> the cron job
On Fri, Mar 29, 2024 at 2:43 AM Adrian Klaver
wrote:
>
>
> On 3/28/24 2:10 PM, sud wrote:
> > Hi, It's postgres 15.4.
> >
> > We want to give required privilege to certain users or roles and ensure
> > to not to provide any elevated privilege. I have below questions,
>
> I would suggest spending
Hello All,
In RDS postgres(version 15.4), we have scheduled partition maintenance
through pg_partman and it's scheduled through pg_cron as below. The same
script has been executed in dev and test environments, and we are seeing
the cron job is scheduled in both environments because we see one
On 3/28/24 2:10 PM, sud wrote:
Hi, It's postgres 15.4.
We want to give required privilege to certain users or roles and ensure
to not to provide any elevated privilege. I have below questions,
I would suggest spending some time here:
https://www.postgresql.org/docs/current/ddl-priv.html
Hi, It's postgres 15.4.
We want to give required privilege to certain users or roles and ensure to
not to provide any elevated privilege. I have below questions,
1)I am seeing in many places, we have "usage on schema" privilege given.
along with "grant select on to " for the objects of
the
On Thu, Mar 28, 2024 at 08:56:59PM +0900, 김명준 wrote:
> Hello,
>
> I am deeply fascinated by the powerful features and flexibility of PostgreSQL
> and wish to share it with more Korean speakers. I am interested in
> contributing
> to the Korean translation of the PostgreSQL official documentation
On Thu, Mar 28, 2024 at 2:27 PM arun chirappurath
wrote:
> Dear all,
>
> I am a new bie in postgres world
>
> Suppose I have accidently deleted a table or deleted few rows ,is it safe
> to drop this table and restore just this table from custom backup to same
> database?
>
By "custom
On 3/28/24 11:27, arun chirappurath wrote:
Dear all,
I am a new bie in postgres world
Suppose I have accidently deleted a table or deleted few rows ,is it
safe to drop this table and restore just this table from custom backup
to same database?
1) You can though depending on when you
Dear all,
I am a new bie in postgres world
Suppose I have accidently deleted a table or deleted few rows ,is it safe
to drop this table and restore just this table from custom backup to same
database?
Or should I create a new database and restore it there and then migrate the
data?
What is
On 3/28/24 08:57, Fire Emerald wrote:
Am 28. März 2024 15:00:06 schrieb Tom Lane :
Fire Emerald writes:
Then i did a pg_restore -d target --verbose -Fc file.dump and saw in the
output this:
5145 0 730750 TABLE subpartitions backends_y2024w03 userA
; depends on: 237
and so on
Op do 28 mrt 2024 om 16:21 schreef Laurenz Albe :
> On Thu, 2024-03-28 at 15:52 +0100, Emond Papegaaij wrote:
> > This works fine most of the time, but sometimes we see this message on
> one of the nodes:
> > pg_rewind: source and target cluster are on the same timeline pg_rewind:
> no rewind
Fire Emerald writes:
> The partitioning must be the problem somehow.
[ shrug... ] You're still not providing any details that would
let somebody else reproduce or diagnose the problem.
https://wiki.postgresql.org/wiki/Guide_to_reporting_problems
regards, tom lane
Am 28. März 2024 15:00:06 schrieb Tom Lane :
Fire Emerald writes:
Then i did a pg_restore -d target --verbose -Fc file.dump and saw in the
output this:
5145 0 730750 TABLE subpartitions backends_y2024w03 userA
;depends on: 237
and so on ...
That is not an error, it's just
On 3/28/24 07:25, Daniel Gustafsson wrote:
On 28 Mar 2024, at 15:22, Adrian Klaver wrote:
On 3/28/24 04:56, 김명준 wrote:
Hello,
I am deeply fascinated by the powerful features and flexibility of PostgreSQL
and wish to share it with more Korean speakers. I am interested in contributing
to the
On 22 Mar 2024, at 17:00, Alban Hertroys wrote:
On Fri, 22 Mar 2024 at 15:01, Nick Renders
wrote:
We now have a second machine with this issue: it is an Intel Mac mini
running macOS Sonoma (14.4) and PostgreSQL 16.2.
This one only has a single Data directory, so there are no multiple
On Thu, 2024-03-28 at 15:52 +0100, Emond Papegaaij wrote:
> * we detach the primary database backend, forcing a failover
> * pgpool selects a new primary database and promotes it
> * the other 2 nodes (the old primary and the other standby) are rewound
>and streaming is resumed from the
Hi,
We develop an application that uses PostgreSQL in combination with Pgpool
as a database backend for a Jakarta EE application (on WildFly). This
application supports running in a clustered setup with 3 nodes, providing
both high availability and load balancing. Every node runs an instance of
rw...@posteo.net writes:
> I had initially made a false assumption that only UNION, CASE, and Related
> Constructs (listed in the documentation) are affected by this.
The examples you show aren't particularly about those things, they
are about use of sub-SELECTs, and specifically about the fact
> On 28 Mar 2024, at 15:22, Adrian Klaver wrote:
>
> On 3/28/24 04:56, 김명준 wrote:
>> Hello,
>> I am deeply fascinated by the powerful features and flexibility of
>> PostgreSQL and wish to share it with more Korean speakers. I am interested
>> in contributing to the Korean translation of the
On 3/28/24 04:56, 김명준 wrote:
Hello,
I am deeply fascinated by the powerful features and flexibility of
PostgreSQL and wish to share it with more Korean speakers. I am
interested in contributing to the Korean translation of the PostgreSQL
official documentation and would like guidance on how
Fire Emerald writes:
> Then i did a pg_restore -d target --verbose -Fc file.dump and saw in the
> output this:
> 5145 0 730750 TABLE subpartitions backends_y2024w03 userA
> ;depends on: 237
> and so on ...
That is not an error, it's just verbose display of one of the items
in the
On Thursday, March 28, 2024, wrote:
>
>
> I've identified a number of cases that suffer from problems caused by the
> type
> resolution algorithm when the "unknown" type is present.
>
This has been brought up many times before, though not for a long while
now. I’d suggest searching the mailing
Hello,
I've identified a number of cases that suffer from problems caused by
the type
resolution algorithm when the "unknown" type is present.
The most common case is that of a UNION query which is even mentioned in the
documentation at
Hello,
I am deeply fascinated by the powerful features and flexibility of
PostgreSQL and wish to share it with more Korean speakers. I am interested
in contributing to the Korean translation of the PostgreSQL official
documentation and would like guidance on how to begin this process.
1. 1. I
Hello everyone,
I created a database dump in postgres 'custom' format using: pg_dump -d
origin --data-only -Fc > file.dump
Then i did a pg_restore -d target --verbose -Fc file.dump and saw in the
output this:
5145 0 730750 TABLE subpartitions backends_y2024w03 userA
;depends on:
28 matches
Mail list logo
