I never came across this before and wonder why?
Regards,
David
Which version? Active session should be green.
Regards,
Chris
On 11/11/2021 21:24，Shaozhong SHI wrote：
I never came across this before and wonder why?
Regards,
David
Hello people,
Please, I am working on a PoC for Real-time Person Identification, and one
of the critical aspects of it is to support both minor misspelling and
phonetic variations of First, Middle, and Last name. Like HarinGton ==
HarrinBton or RaphEAl == RafAEl. It's working for longer names, but
Sorry, please remove this question, I sent it to the wrong mailing list.
On Thu, Nov 11, 2021 at 11:20 AM Jean Baro wrote:
> Hello people,
>
> Please, I am working on a PoC for Real-time Person Identification, and one
> of the critical aspects of it is to support both minor misspelling and
> pho
On Thu, 2021-11-11 at 13:24 +, Shaozhong SHI wrote:
> I never came across this before and wonder why?
I think I remember that means that the session is stuck behind a lock,
but I am not certain. Look for "wait_event_type" in "pg_stat_statement".
Yours,
Laurenz Albe
--
Cybertec | https://www
Hi everyone,
every few weeks I use Postgres ability, to import huge data sets very
fast by means of "unlogged tables". The bulk load (consisting of plenty
"copy"- & DML-Stmts) and the spatial index creation afterwards, takes
about 5 hours on a proper server (pg12.7 & PostGIS-Extension). After
On Thu, Nov 11, 2021 at 11:39 AM wrote:
> After
> that all unlogged tables remain completely unchanged (no
> DML-/DDL-Statements). Hence all of my huge unlogged, "static" tables get
> never "unclean" and should not be truncated after a server crash.
>
The server cannot make this assumption so it
Hello. I write for the following reason: I had configured a pg_hba.conf
file, which I am using with some debian virtual machines, to be able to
communicate between two different virtual machines.
Well, it turns out that at one point when I was using my virtual machines,
suddenly and unexpectedly,
On 11/11/21 17:14, Yessica Brinkmann wrote:
Hello. I write for the following reason: I had configured a pg_hba.conf
file, which I am using with some debian virtual machines, to be able to
communicate between two different virtual machines.
Well, then, I went to modify my pg_hba.conf file so th
Hello everyone??
I added a ?? operator to scan.l. The sqrt function is still used internally,
but there is a problem now, which affects the := and .. operators of the
database.
# Description of Requirement:
1??select ?? num1; function
2??The value of num1 is required to be: [0,922337203685477
On Thu, Nov 11, 2021 at 8:42 PM 孤傲小二～阿沐 <2903807...@qq.com> wrote:
> I added a √ operator to scan.l.
>
Why?
> The sqrt function is still used internally, but there is a problem now,
> which affects the := and .. operators of the database.
>
Someone else will have to volunteer their time to cov
Hello, thank you for your busy reply. The purpose of this development is to
learn PostgreSQL's lexical parsing process in depth, and it has no substantial
effect. You can ignore this. The limitation of the scene can also be ignored.
The problem now is that select ?? 1024; can be used normally,
Guessing here but try a different symbol, something in ASCII (I'm guessing
the current choice is not). The fact that you added your symbol directly
above dotdot and colonequals is suspicious...
David J.
On Thu, Nov 11, 2021, 21:32 孤傲小二～阿沐 <2903807...@qq.com> wrote:
> Hello, thank you for your b
Hello, do you mean there is a problem with this symbol itself? But so far,
there are no problems when using it.
sqrt "??"
So where do you think this should be added? I tried to change the position but
the error still persists
-- --
??:
"=?gb18030?B?ucKwwdChtv6hq7Ci4+U=?=" <2903807...@qq.com> writes:
> # Description of Requirement:
> 1¡¢select ¡Ì num1; function
> 2¡¢The value of num1 is required to be: [0,9223372036854775807]
> 3¡¢¡Ì The operation does not allow decimals
Looks suspiciously like a homework assignment.
> I have no
Hello, I think what you said is right, it should be the problem. But I don't
know what to do in the lexical analysis system of plpgsql to solve this problem.
-- 原始邮件 --
发件人:
On Thursday, November 11, 2021, 孤傲小二～阿沐 <2903807...@qq.com> wrote:
> Hello, I think what you said is right, it should be the problem. But I
> don't know what to do in the lexical analysis system of plpgsql to solve
> this problem.
>
>
“To match” means keep two copies identical, in this case manual
Hello everyone, I modified src/fe_utils/psqlscan.l
src/interfaces/ecpg/preproc/pgc.l src/pl/plpgsql/src/pl_gram.y according to his
suggestion to keep scan.l gram.y consistent , But still error
-- --
??:
This function is already OK, I think tom is correct. After I modified the
relevant files, the problem was solved.
Now my newly added functions and the regression test of the database itself are
all OK
Thank you both for your continuous support and blessings from China!
sqrt_bigint_v2.patch
D
This function is already OK, I think tom is correct. After I modified the
relevant files, the problem was solved.
Now my newly added functions and the regression test of the database itself are
all OK
Thank you both for your continuous support and blessings from China!
sqrt_bigint_v2.patch
D
On Thu, 2021-11-11 at 18:39 +, sch...@posteo.de wrote:
> every few weeks I use Postgres ability, to import huge data sets very
> fast by means of "unlogged tables". The bulk load (consisting of plenty
> "copy"- & DML-Stmts) and the spatial index creation afterwards, takes
> about 5 hours on
21 matches
Mail list logo
