Hello, it looks like I've run into the same issue as you. I exhausted the disk
space while executing DDL operations, and then after crash recovery, I found
there were orphaned files.
I believe the reason is that due to the lack of space, some of the WAL logs were
not persisted, such as the abort-ty
On Fri, Mar 22, 2024 at 11:25 AM Fred Habash wrote:
> Facing an issue where sometimes humans login to a database and run DDL
> statements causing a long locking tree of over 1000 waiters. As a
> workaround, we asked developers to always start their DDL sessions
> with 'SET lock_timeout = 'Xs'.
>
On 2024-03-25 23:44, Merlin Moncure wrote:
On Mon, Mar 25, 2024 at 4:43 AM Dominique Devienne
wrote:
Hi. Anything you can share? OSS? Doesn't look like it...
If it's not, a more details higher level architecture overview would
be
nice.
let me float that, I would love to project-ize this.
On Mon, Mar 25, 2024 at 9:49 AM Christophe Pettus wrote:
>
>
> > On Mar 25, 2024, at 02:50, Thiemo Kellner
> wrote:
> > My bad. I was under the impression that the create table statement was
> an atomic process/transaction with all its bells and whistles for
> constraints and keys, instead of a
On 3/25/24 00:18, Bandi, Venkataramana - Dell Team wrote:
Hi,
Please find my inline comments for your questions.
Regards,
Venkat
Internal Use - Confidential
-Original Message-
From: Adrian Klaver
Sent: Tuesday, March 19, 2024 9:33 PM
To: Bandi, Venkataramana - Dell Team ; Greg Sabin
> On Mar 25, 2024, at 07:20, Daniel Gustafsson wrote:
>
>> On 25 Mar 2024, at 15:09, Tom Lane wrote:
>
>> My initial reaction is that we should warn only when the command
>> is a complete no-op, that is none of the mentioned privileges
>> matched.
>
> That's my gut reaction too,
I think t
> On 25 Mar 2024, at 15:09, Tom Lane wrote:
> My initial reaction is that we should warn only when the command
> is a complete no-op, that is none of the mentioned privileges
> matched.
That's my gut reaction too,
--
Daniel Gustafsson
Christophe Pettus writes:
> Right now, if you do a REVOKE that doesn't actually revoke anything, it works
> silently. This can be a bit of a foot-gun. For example:
> CREATE FUNCTION f() RETURNS int as $$ SELECT 1; $$ LANGUAGE sql;
> REVOKE EXECUTE ON FUNCTION f() FROM lowpriv;
> Na
> On 25 Mar 2024, at 14:54, Christophe Pettus wrote:
>
> Right now, if you do a REVOKE that doesn't actually revoke anything, it works
> silently. This can be a bit of a foot-gun. For example:
>
> CREATE FUNCTION f() RETURNS int as $$ SELECT 1; $$ LANGUAGE sql;
> REVOKE EXECUTE ON
Right now, if you do a REVOKE that doesn't actually revoke anything, it works
silently. This can be a bit of a foot-gun. For example:
CREATE FUNCTION f() RETURNS int as $$ SELECT 1; $$ LANGUAGE sql;
REVOKE EXECUTE ON FUNCTION f() FROM lowpriv;
Naively, it might be expected that
> On Mar 25, 2024, at 02:50, Thiemo Kellner wrote:
> My bad. I was under the impression that the create table statement was an
> atomic process/transaction with all its bells and whistles for constraints
> and keys, instead of a succession of alter statements.
That may be a bit judgmental. :
Hi,
Please find my inline comments for your questions.
Regards,
Venkat
Internal Use - Confidential
-Original Message-
From: Adrian Klaver
Sent: Tuesday, March 19, 2024 9:33 PM
To: Bandi, Venkataramana - Dell Team ; Greg
Sabino Mullane
Cc: pgsql-general@lists.postgresql.org; Kishore,
On Mon, Mar 25, 2024 at 4:43 AM Dominique Devienne
wrote:
> On Sat, Mar 23, 2024 at 3:13 AM Merlin Moncure wrote:
>
>> On Fri, Mar 22, 2024 at 6:58 AM ushi wrote:
>>
>>> the idea to implement a job queuing system using PostgreSQL.
>>>
>>
>> I wrote an enterprise scheduler, called pgtask, which
Am 25.03.2024 um 07:59 schrieb Laurenz Albe:
On Sun, 2024-03-24 at 17:32 +0100, Thiemo Kellner wrote:
How can that be forgotten? This information ends up in the data
catalogue eventually!
It *is* stored in the catalog.
But if you add a primary key, that is tantamount to saying
ALTER TA
On Sat, Mar 23, 2024 at 3:13 AM Merlin Moncure wrote:
> On Fri, Mar 22, 2024 at 6:58 AM ushi wrote:
>
>> the idea to implement a job queuing system using PostgreSQL.
>>
>
> I wrote an enterprise scheduler, called pgtask, which ochestates a very
> large amount of work [...]
>
Hi. Anything you ca
My bad as always. Having the refresh after the filling of the tables
does the trick. Thanks for your help.
16 matches
Mail list logo
