On Fri, Sep 8, 2023 at 1:41 PM Les wrote:
>
> Dear fellow PostgreSQL users,
>
> Today I caught this with postgresql v15, while restoring a database with
> psql --echo-errors --quiet. (The dump was made using pg_dump -Fp).
>
> It logged lots of these messages:
>
> setval
>
>1001
>
On 9/8/23 12:36, Les wrote:
Dear fellow PostgreSQL users,
Today I caught this with postgresql v15, while restoring a database with
psql --echo-errors --quiet. (The dump was made using pg_dump -Fp).
It logged lots of these messages:
setval
1001
(1 row)
In other words, it
Dear fellow PostgreSQL users,
Today I caught this with postgresql v15, while restoring a database with
psql --echo-errors --quiet. (The dump was made using pg_dump -Fp).
It logged lots of these messages:
setval
1001
(1 row)
In other words, it logs **some** things that are not er
On 9/7/23 23:29, Les wrote:
I'm trying to migrate a database from version 11 to version 15.
I have created a dump file on v11:
pg_dump --dbname=not_telling -Fc --no-owner > dump
--no-owner is ignored for non-text outputs. It is handled on the
pg_restore end.
Then I was trying to import i
On 9/8/23 04:25, Nature Conservation Geovista Space wrote:
Dear Pg-users,
I am coming back to Postgres/PostGIS after a few years. I am dealing
with a big database with a lot of geometries and too many vertices.
Postgres version?
PostGIS version?
OS and version?
Is this a physical machine o
gzh writes:
> In the Release Notes for PostgreSQL 12.14, we saw the following change:
> https://www.postgresql.org/docs/release/12.14/
>> Add recursion and looping defenses in subquery pullup (Tom Lane)
>> A contrived query can result in deep recursion and unreasonable amounts of
>> time spent
Hello friends,
I want to migrate a large Oracle table to PostgreSQL, which is
approximately 200GB in size and includes a LOB segment. This table has a
primary key column named "ID," which increments by one unit (similar to a
sequence). During the migration of this large table, sometimes the proces
Dear Pg-users,
I am coming back to Postgres/PostGIS after a few years. I am dealing with a
big database with a lot of geometries and too many vertices.
After hours running a query to Subdivide, I get this Postgres error
*2023-09-08 02:11:23.745 BST [328594] postgres@database ERROR: could not
e
On 9/7/23 23:51, Sai Teja wrote:
Thank you so much for all your responses.
I just tried with Hash, GIN etc
But it didn't worked. And I think it is because of "Xpath" expression
which I used in the index create command.
But is there any alternative way to change this Xpath? Since I need to
p
On Fri, Sep 8, 2023 at 11:39 AM Dominique Devienne
wrote:
> On Thu, Sep 7, 2023 at 10:22 PM Tom Lane wrote:
>
>> Erik Wienhold writes:
>> > Looks like "Huge input lookup" as reported in [1] (also from Sai) and
>> that
>> > error is from libxml.
>>
>> Ah, thanks for the pointer. It looks like f
On Thu, Sep 7, 2023 at 10:22 PM Tom Lane wrote:
> Erik Wienhold writes:
> > Looks like "Huge input lookup" as reported in [1] (also from Sai) and
> that
> > error is from libxml.
>
> Ah, thanks for the pointer. It looks like for the DOCUMENT case,
> we could maybe relax this restriction by pass
El día jueves, septiembre 07, 2023 a las 12:33:06 -0400, Stephen Frost escribió:
> * Matthias Apitz (g...@unixarea.de) wrote:
> > >
> > > There's ongoing work happening for TDE support and we'd love to hear
> > > from folks who would like to see it included. You can expect an updated
> > > patch
Am Mittwoch, dem 06.09.2023 um 20:42 +0200 schrieb Imre Samu:
> Maybe you have to increase the "*--stop-timeout" value
That is totally unrelated in my case, it is an anonymous volume anyway
which gets created on start and deleted afterwards.
Torsten
13 matches
Mail list logo
