Hi
pá 4. 2. 2022 v 7:02 odesílatel rob stan napsal:
> Hello,
>
> We have "pgq" extensions on our clusters when I am trying to upgrade from
> 9.6.24 to 14.1 with pg_upgrade --link method, i am getting error;
>
>
> First i was getting this error ;
>
> could not load library "$libdir/pgq_lowlevel":
Hello,
We have "pgq" extensions on our clusters when I am trying to upgrade from
9.6.24 to 14.1 with pg_upgrade --link method, i am getting error;
First i was getting this error ;
could not load library "$libdir/pgq_lowlevel": ERROR: could not access
file "$libdir/pgq_lowlevel": No such file o
On Wed, Feb 2, 2022 at 4:26 PM Tom Lane wrote:
>
> "David G. Johnston" writes:
> > Given we don't have a regexp_count function this isn't surprising...
>
> FYI, it's there in HEAD.
>
> In the meantime, you could possibly do something like
>
> =# select count(*) from regexp_matches('My High Street
Tomas,
thank you! The query:
select 1 from data as d, data_class as dc
where dc.data_id = d.id and d.id > 205284974
and dc.data_id > 205284974 -- new condition
order by d.id
limit 1000;
totally solved it - it is now fast under all conditions! I thought
that the optimizer woul
Thanks David.
On Fri, Feb 4, 2022 at 9:44 AM David G. Johnston
wrote:
> On Thu, Feb 3, 2022 at 9:03 PM aditya desai wrote:
>
>>
>> For Postgres_Fdw we have below command to increase the fetch size.
>>
>> ALTER SERVER ServerName OPTIONS ( fetch_size='5');
>>
>> Do we have a similar command f
On Thu, Feb 3, 2022 at 9:03 PM aditya desai wrote:
>
> For Postgres_Fdw we have below command to increase the fetch size.
>
> ALTER SERVER ServerName OPTIONS ( fetch_size='5');
>
> Do we have a similar command for oracle_fdw?
>
>
The SQL command itself is generic. The option name that seems
Hi,
For Postgres_Fdw we have below command to increase the fetch size.
ALTER SERVER ServerName OPTIONS ( fetch_size='5');
Do we have a similar command for oracle_fdw?
Thanks in advance.
Regards,
Aditya.
> If Michael's analysis were accurate, I'd agree that there is a robustness
> issue, but I don't think there is. See timeout.c:220:
Actually that only sets a new timer after the nearest timeout has expired.
The pattern I was seeing went like this:
1. Command occurs during which a signal was not
Hi Vijaykumar
Thank you so much for taking out so much of your time to recreate the bug.
I checked the max_logical_replication_workers on both the nodes and they
are set at 4 at the moment.
The reason why it is failing is that there are 3 existing replications on
the target node already and when
I would guess that autovacuum is analyzing the table and causing the stats
to change which is resulting in different estimates that result in
different plans. Unless you can get the estimate much more accurate, you
won't get far with expecting a stable plan that performs well.
How is data_class_pk
On 2/3/22 3:29 PM, saket bansal wrote:
Hi, I am trying to schedule pg_cron to generate a set of commands and then
run them. E.g |select 'vacuum freeze '||table_name from
inventory_for_vacuum \gexec| . This works well at command line, but when
scheduled in pg_cron, it fails with syntax error |ER
Can't you use a do script to construct and execute the statement?
>
On Fri, Feb 4, 2022 at 8:11 AM Matthias Apitz wrote:
> On my FreeBSD laptop the same file sorts as
>
> guru@c720-r368166:~ $ LANG=de_DE.UTF-8 sort swd
> A
> ゲアハルト・A・リッター
> ゲルハルト・A・リッター
> チャールズ・A・ビアード
> A010STRUKTUR
> A010STRUKTUR
> A010STRUKTUR
> A0150SUPRALEITER
Wow, so it's one thing to have a
On Thu, Feb 3, 2022 at 2:29 PM saket bansal wrote:
> Hi, I am trying to schedule pg_cron to generate a set of commands and then
> run them. E.g select 'vacuum freeze '||table_name from
> inventory_for_vacuum \gexec . This works well at command line, but when
> scheduled in pg_cron, it fails with
On 2/3/22 1:29 PM, saket bansal wrote:
Hi, I am trying to schedule pg_cron to generate a set of commands and
then run them. E.g |select 'vacuum freeze '||table_name from
inventory_for_vacuum \gexec| . This works well at command line, but when
scheduled in pg_cron, it fails with syntax error |ER
Hi, I am trying to schedule pg_cron to generate a set of commands and then
run them. E.g select 'vacuum freeze '||table_name from inventory_for_vacuum
\gexec . This works well at command line, but when scheduled in pg_cron, it
fails with syntax error ERROR: syntax error at or near "\" .
Since vacuu
Hi, Peter, Interesting.
On Thu, 3 Feb 2022 at 19:48, Peter J. Holzer wrote:
> On 2022-02-02 08:00:00 +, Shaozhong SHI wrote:
> > regex - Regular Expression For Duplicate Words - Stack Overflow
> >
> > Is there any example in Postgres?
>
> It's pretty much the same as with other regexp diale
the random_page_cost = 1.2 and seq_page_cost= 1 in my setup are the
same. I also run the vacuum analyze on all tables. I have no idea why
the optimizer thinks that the merge on 2 200M row tables is faster
than 50 index lookups, other than it "thinks" that in-memory merges
are very low cost regardle
On Fri, 4 Feb 2022 at 01:03, A Shaposhnikov wrote:
> I made a mistake yesterday claiming that the created statistics
> changed the row counts in the estimates - it did not - I looked at
> the wrong query yesterday. In the correct query plan the row estimate
> still differs from the actual by man
On 2022-02-02 08:00:00 +, Shaozhong SHI wrote:
> regex - Regular Expression For Duplicate Words - Stack Overflow
>
> Is there any example in Postgres?
It's pretty much the same as with other regexp dialects: User word
boundaries and a word character class to match any word and then use a
back
I made a mistake yesterday claiming that the created statistics
changed the row counts in the estimates - it did not - I looked at
the wrong query yesterday. In the correct query plan the row estimate
still differs from the actual by many orders of magnitude:
Nested Loop (cost=1.01..27584834.53
On Thu, Feb 3, 2022, 8:55 PM wrote:
> Hi,
>
>
>
> I have some questions regarding the indexing and sampling API.
>
> My aim is to implement a variant of progressive indexing as seen in this
> paper (link). To summarize,
>
> I want to implement a variant of online aggregation, where an aggregate
>
El día jueves, febrero 03, 2022 a las 10:00:37 -0500, Tom Lane escribió:
> Matthias Apitz writes:
> > El día jueves, febrero 03, 2022 a las 11:14:55 +0100, Matthias Apitz
> > escribió:
> >> With ESQL/C on a PostgreSQL 13.1 server I see the result of this query:
> >> select katkey,normform from s
trimming the email, to avoid noise.
I spent a lot of time trying multiple options/combinations and finally
managed to replicate your debug output.
this is when i have ,
postgres=# show max_logical_replication_workers;
* max_logical_replication_workers*
-
* 2*
(1 ro
Simon Riggs writes:
> On Thu, 3 Feb 2022 at 06:25, Michael Harris wrote:
>> Some of these functions trigger fetching of remote resources, for
>> which a timeout is set using `alarm`. The function unfortunately does
>> not re-establish any pre-existing interval timers after it is done,
>> which le
Hi, David,
Many thanks.
I am investigating into transformation of data quality validation through
automation with application of Postgres/PostGIS.
Regards,
David
On Thu, 3 Feb 2022 at 13:00, David G. Johnston
wrote:
>
>
> On Thursday, February 3, 2022, Shaozhong SHI
> wrote:
>
>>
>> Is it c
Hi,
I have some questions regarding the indexing and sampling API.
My aim is to implement a variant of progressive indexing as seen in this
paper (link
). To summarize,
I want to implement a variant of online aggregation, where an aggregate
query (Like Sum, Average, etc.) is answered in re
On Thu, 2022-02-03 at 20:24 +0530, Rama Krishnan wrote:
> How do we take care of database character set when trying
> to migrate from oracle to postgres
If NLS_SORT and NLS_COMP are set to German in Oracle,
just create the PostgreSQL to a German collation to get
a similar behavior.
Yours,
Laurenz
Matthias Apitz writes:
> El día jueves, febrero 03, 2022 a las 11:14:55 +0100, Matthias Apitz escribió:
>> With ESQL/C on a PostgreSQL 13.1 server I see the result of this query:
>> select katkey,normform from swd_anzeige where normform >= 'A' ORDER BY ASC;
>> coming out in this order:
>> ...
>> I
Julien Rouhaud writes:
> On Thu, Feb 03, 2022 at 05:39:57PM +0530, Bharath Rupireddy wrote:
>> ... Instead, it would be better
>> if the server emits a single log with all the insufficient
>> parameters(max_connections, max_worker_processes, max_wal_senders,
>> max_prepared_transactions and max_lo
On Thu, Feb 03, 2022 at 05:39:57PM +0530, Bharath Rupireddy wrote:
>
> Agree that the standby should atleast have the capacity that the
> primary has in terms of resources. But what I don't like about that
> code is calling RecoveryRequiresIntParameter for each parameter
> separately and crashing
On Thursday, February 3, 2022, Shaozhong SHI wrote:
>
> Is it correct to say that this ?: construction of a regex can be applied
> for checking whether cell values meet specifications?
>
>>
>>
It does exactly what our examples shows it does. I don’t understand what
you mean above but if that hel
On Thu, Feb 3, 2022 at 3:17 PM Julien Rouhaud wrote:
>
> Hi,
>
> On Thu, Feb 03, 2022 at 10:36:37AM +0100, Luca Ferrari wrote:
> > Hi all,
> > running PostgreSQL 14, physical replication with slot, after changing
> > (increasing) the max_connections on the primary, I had this message at
> > a rest
El día jueves, febrero 03, 2022 a las 11:14:55 +0100, Matthias Apitz escribió:
>
> Hello,
>
> With ESQL/C on a PostgreSQL 13.1 server I see the result of this query:
>
> select katkey,normform from swd_anzeige where normform >= 'A' ORDER BY ASC;
>
> coming out in this order:
>
> query: fetch
Hello,
With ESQL/C on a PostgreSQL 13.1 server I see the result of this query:
select katkey,normform from swd_anzeige where normform >= 'A' ORDER BY ASC;
coming out in this order:
query: fetch swd_anzeige_seq
RESULT: A
query: fetch swd_anzeige_seq
RESULT: ゲアハルト・A・リッター
query: fetch swd_anzeig
Hi,
On Thu, Feb 03, 2022 at 10:36:37AM +0100, Luca Ferrari wrote:
> Hi all,
> running PostgreSQL 14, physical replication with slot, after changing
> (increasing) the max_connections on the primary, I had this message at
> a restart from the standby:
>
> DETAIL: max_connections = 100 is a lower
* *Basic Connectivity from target(subscriber) to source (Publisher)-*
postgres@targethost:~$ psql -h sourcedb-vip --port=5432 --user=dba -d
sourcedb
Password for user dba:
psql (13.3)
Type "help" for help.
sourcedb=#
* *Create Publication*
sourcedb=# CREATE PUBLICATION omx_archive FOR TABLE
sam
On Thu, Feb 3, 2022, 3:07 PM Luca Ferrari wrote:
> Hi all,
> running PostgreSQL 14, physical replication with slot, after changing
> (increasing) the max_connections on the primary, I had this message at
> a restart from the standby:
>
> DETAIL: max_connections = 100 is a lower setting than on t
Hi all,
running PostgreSQL 14, physical replication with slot, after changing
(increasing) the max_connections on the primary, I had this message at
a restart from the standby:
DETAIL: max_connections = 100 is a lower setting than on the primary
server, where its value was 300.
and the standby d
Many thanks, Tom,
select regexp_matches('My High Street', '(?:[A-Z][a-z]+[\s]*)+', 'g');
looks very interesting.
I did read the documentation, but found it is difficult to read.
Particularly, the documentation on the use ?: does not state clear sense.
There is only limited explanation on ?:.
Is
On Thu, 3 Feb 2022 at 06:25, Michael Harris wrote:
>
> Hi again
>
> Some good news. After some more debugging & reflection, I realized
> that the likely cause is one of our own libraries that gets loaded as
> part of some custom functions we are using.
>
> Some of these functions trigger fetching
On Thu, 3 Feb 2022 at 12:44, Abhishek Bhola
wrote:
> Hi Vijaykumar,
>
> I checked the pg_subscription_rel and all the tables in that subscription
> are in the state - i (initialize).
> I also tried creating a new publication on the source DB with just one
> table and tried to subscribe it, it doe
42 matches
Mail list logo
