On 9/15/25 00:16, ma lz wrote:
To fix CVE-2025-8714, PG introduce \restrict , but if we use python
( like psycopg2), it does not support slash command.
The backslash commands are specific to psql:
https://www.postgresql.org/docs/current/app-psql.html
Per the release notes:
https://www.postgr
On 9/10/25 00:41, Ellen Allhatatlan wrote:
Hi, and thanks for your input,
The author brings up threaded vs multi-process. That's an old old old old old
conversation that has been shown there is no clear better way.
This is where things become interesting. Firebird actually has 3
process/th
I'm trying to troubleshoot the slowness issue with pg_restore and stumbled
across a recent post about pg_restore scanning the whole file :
> "scanning happens in a very inefficient way, with many seek calls and
small block reads. Try strace to see them. This initial phase can take
hours in a huge
On Tue, Sep 9, 2025 at 7:11 PM Ron Johnson wrote:
> On Tue, Sep 9, 2025 at 8:41 PM Justin wrote:
>
>>
>> On autonomous transactions we have procedures now that allow transactions
>> inside of transactions that can be committed and rollbacked. that has been
>> around for several years now.
>>
>
On 9/10/25 08:11, Ron Johnson wrote:
On Wed, Sep 10, 2025 at 11:08 AM Ellen Allhatatlan
mailto:ellenallhatat...@gmail.com>> wrote:
[snip]
So, you have table X - it has 2M rows (say, 0.5 GB) in the first file
(along with all the other tables). The 2GB limit is hit, more data is
added
> On Sep 20, 2025, at 9:58 AM, Adrian Klaver wrote:
> On 9/20/25 09:26, Rob Sargent wrote:
>>> So the problem goes away once you’ve reindexed yet you claim it’s
>>> consistent? What are you doing to get the problem to recur after you’ve
>>> done reindex to make it work?
>>> David
>> I was as
On Thu, Sep 11, 2025 at 5:38 AM Ellen Allhatatlan <
ellenallhatat...@gmail.com> wrote:
> "A last aspect of our design concerns the operating system process
> structure. Currently, POSTGRES runs as one process for each active
> user. This was done as an expedient to get a system operational as
> qu
On Wed, Sep 10, 2025 at 11:08 AM Ellen Allhatatlan <
ellenallhatat...@gmail.com> wrote:
[snip]
> So, you have table X - it has 2M rows (say, 0.5 GB) in the first file
> (along with all the other tables). The 2GB limit is hit, more data is
> added. 0.7 GB is added to table X - these records go into
On 9/20/25 09:26, Rob Sargent wrote:
So the problem goes away once you’ve reindexed yet you claim it’s consistent?
What are you doing to get the problem to recur after you’ve done reindex to
make it work?
David
I was assuming the OP has a dump of the affected condition and is restoring
(
> So the problem goes away once you’ve reindexed yet you claim it’s consistent?
> What are you doing to get the problem to recur after you’ve done reindex to
> make it work?
>
> David
I was assuming the OP has a dump of the affected condition and is restoring
(and perhaps re-fixing). No?
On Friday, September 19, 2025, Wim Rouquart wrote:
>
> >> Does this problem keep happening, or has it only happened once?
>
>
>
> It is consistent on this database/index, haven’t noticed it anywhere else
> yet luckily. Seems to be a one-off.
>
>
So the problem goes away once you’ve reindexed yet
On 9/19/25 02:29, Wim Rouquart wrote:
Internal
Does this problem keep happening, or has it only happened once?
It is consistent on this database/index, haven’t noticed it anywhere
else yet luckily. Seems to be a one-off.
The above is not clear to me. One-off as for this database/index on
Internal
>> Internal
>>
>>
>> Hello,
>>
>>When doing a pg_dump of one of our databases one of the tables primary
>> keys doesn’t get exported. Pg_dump just skips this index, without any
>> warning whatsoever (verbose mode was used to doublecheck).
> What is the complete table definition?
CREATE
Internal
Hello,
When doing a pg_dump of one of our databases one of the tables
primary keys doesn’t get exported. Pg_dump just skips this index,
without any warning whatsoever (verbose mode was used to doublecheck).
>>
>>> What is the complete table definition?
>>
>> CREAT
Internal
Hello,
When doing a pg_dump of one of our databases one of the tables primary keys
doesn’t get exported. Pg_dump just skips this index, without any warning
whatsoever (verbose mode was used to doublecheck).
When doing a REINDEX the issue is fixed.
As this seems to me to be some form
15 matches
Mail list logo
