On Mon, Jun 7, 2021 at 07:53:30PM +0200, Francisco Olarte wrote:
> message like yours in 5-10 seconds, properly scanning a top posted one
> takes much longer. So normally I stop reading at the quote and discard
> the message if I have not understood with what I have read UNLESS it's
> from my moth
Marc Millas schrieb am 03.06.2021 um 22:51:
on a table we need a primary key and to get a unique combinaison, we need 3
columns of that table:
1 of type integer,
1 of type text,
1 of type geometry
creating the PK constraint doesn work: (even with our current small data set)
ERROR: index row si
Marc Millas writes:
> I know, its clearly stated in postgres doc about btree," The only
> limitation is that an index entry cannot exceed approximately one-third of
> a page (after TOAST compression, if applicable)."
Yup.
> is there any plan to adress this ?
No. The cost/benefit ratio seems co
On Tuesday, June 8, 2021, Marc Millas wrote:
>
> but as this looks quite hard coded, it means that for long utf8 things
> the data length is not so long before hitting the limit.
>
> is there any plan to adress this ?
>
None that I’ve seen, and I don’t expect to see one either. Mainly because
Cristal clear !
and it have to be the case as my test was done with some not so random data.
but this mean that we cannot put a bunch of datatypes in a PK, as soon as
it may be longer than 2701.
I know, its clearly stated in postgres doc about btree," The only
limitation is that an index entry can
On 2021-06-08 18:30:16 +0200, Marc Millas wrote:
> the only pb observed is the size of the object accepted. if the geom is a bit
> "big" then the index errors.about btree size of index object.
> but if I create a table test_l with a text column blabla as a PK, and insert a
> 100 000 character long
quite funny to see how a tech question seems to end into an english grammar
thing :-)
quote
> You make this sound like an either-or proposition,
While he is talking about *a* primary key, it should be *the* primary
key. There can be only one (that's why it is the primary key).
There can be sever
On Tue, 8 Jun 2021, Karsten Hilbert wrote:
The problem source is postgres telling me it cannot connect to the database
via TCP/IP
but I can do so directly using psql:
via UNIX domain sockets.
Karsten,
That's because psql is direct while PyQt5-5.12.3 cannot access postgres-12.x
tables. I'm wor
On Mon, 7 Jun 2021, Adrian Klaver wrote:
2021-06-07 10:36:38.330 PDT [29537] LOG: database system is ready to accept
connections
2021-06-07 14:19:45.491 PDT [31353] ERROR: column pg_attrdef.adsrc does not
exist at character 128
"
Adrian,
Postgres dropped the pg_attrdev.adsrc column from t
Thanks Guillaume. After this change the error message will even be clearer in
French than in the original version in fact.
Regards,
Phil
De : Guillaume Lelarge
Envoyé : mardi 8 juin 2021 13:21
À : Phil Florent
Cc : pgsql-gene...@postgresql.org
Objet : Re: pg 13
Le mar. 8 juin 2021 à 13:15, Guillaume Lelarge a
écrit :
> Hi,
>
> Le mar. 8 juin 2021 à 12:11, Phil Florent a
> écrit :
>
>> Hi,
>>
>> I had forgotten to include a restore_command and my standby database did
>> not start (expected behavior) but the error message puzzled me :
>>
>> select versio
Hi,
Le mar. 8 juin 2021 à 12:11, Phil Florent a
écrit :
> Hi,
>
> I had forgotten to include a restore_command and my standby database did
> not start (expected behavior) but the error message puzzled me :
>
> select version();
>
> version
>
Hi,
I had forgotten to include a restore_command and my standby database did not
start (expected behavior) but the error message puzzled me :
select version();
version
---
13 matches
Mail list logo
