PegoraroF10 writes:
> CREATE FUNCTION public.fntextonumero(finteger public.i32, ftext text)
> RETURNS boolean
> LANGUAGE sql STABLE
> AS $$
> SELECT ftext = finteger::text;
> $$;
Huh. The crash goes away if you change that to
SELECT finteger::text = ftext;
It looks like ExecInitSu
Well, I didn´t know where was the problem exactly, then ...
The entire script to see that problem is
create domain public.i32 as integer;
CREATE FUNCTION public.fntextonumero(ftext text, finteger public.i32)
RETURNS boolean
LANGUAGE sql STABLE
AS $$
SELECT ftext = finteger::text;
$$;
C
On 2020-Aug-14, PegoraroF10 wrote:
> CREATE FUNCTION public.fntextonumero(ftext text, finteger public.i32)
How is public.i32 defined?
--
Álvaro Herrerahttps://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
And the operator function, just to you know, is only a conversion to text
CREATE FUNCTION public.fntextonumero(ftext text, finteger public.i32)
RETURNS boolean
LANGUAGE sql STABLE
AS $$
SELECT ftext = finteger::text;
$$;
CREATE FUNCTION public.fntextonumero(finteger public.i32, ftext te
PegoraroF10 writes:
> And I have created these two operators a long time ago.
> CREATE OPERATOR public.= (
> FUNCTION = public.fntextonumero,
> LEFTARG = text,
> RIGHTARG = public.i32
> );
> CREATE OPERATOR public.= (
> FUNCTION = public.fntextonumero,
> LEFTARG = public.i32,
It works, shouldn´t but works. Results False
And I have created these two operators a long time ago.
CREATE OPERATOR public.= (
FUNCTION = public.fntextonumero,
LEFTARG = text,
RIGHTARG = public.i32
);
CREATE OPERATOR public.= (
FUNCTION = public.fntextonumero,
LEFTARG = publ
PegoraroF10 writes:
> So, how can I know which custom operator is being used on that comparison ?
You tell us. I don't know of any common extension that would create
a "smallint = text" operator. (A variant theory is that you didn't
make a new operator, but an implicit cast from smallint to tex
Correct, on yours it gives an error message, but on mine it tries to execute
and goes to recovery.
So, how can I know which custom operator is being used on that comparison ?
--
Sent from: https://www.postgresql-archive.org/PostgreSQL-general-f1843780.html
Ok, it works if I cast TipoRecebimento to text.
(TipoRecebimento::text in (select substring(VarValue from 3) from Var where
Name = '/Config/TipoRecebimentoCancelamento'))
But now, how can I know what custom operator it´s trying to use, because
some day I can get in troubles again because that.
PegoraroF10 writes:
> This is the way you can test to push your server immediatelly to recovery
> mode. This one you´ll get the problem instantaneously, differently from the
> last one which you have to wait a long time to happen.
When I try this I get
ERROR: operator does not exist: smallint =
This is the way you can test to push your server immediatelly to recovery
mode. This one you´ll get the problem instantaneously, differently from the
last one which you have to wait a long time to happen.
A master detail relation with an additional table of configurations. Usually
this master has
PegoraroF10 writes:
> Hi Michael, so sorry for the delay. I did never had that problem again, so
> tougth it was solved, but seems not. We have two different SQL which pushs
> server to recovery mode. This SQL is the hardest one, because you´ll have to
> wait some time to get the error. Just runs
Hi Michael, so sorry for the delay. I did never had that problem again, so
tougth it was solved, but seems not. We have two different SQL which pushs
server to recovery mode. This SQL is the hardest one, because you´ll have to
wait some time to get the error. Just runs this SQL, opens your HTOP and
sorry, it´s a missing part of the CTE
that constant should be on beginning part of it.
with feriados as (
SELECT dia, repete
FROM (
VALUES ('2014-10-11'::DATE, FALSE), ('2014-10-13', FALSE),
('2014-10-14', FALSE), ('2014-10-15', FALSE), ('2014-10-16', FALSE),
('2014-10-17', FALS
On Wed, 2019-02-13 at 05:32 -0700, PegoraroF10 wrote:
> is a sql FROM VALUES, why do you need tables ?
>
>
I can see that, however:-
ERROR: relation "col_diasaula" does not exist
Position: 7477
[SQL State: 42P01]
Is that a table, view or a missing CTE?
is a sql FROM VALUES, why do you need tables ?
--
Sent from: http://www.postgresql-archive.org/PostgreSQL-general-f1843780.html
Hello Marcos,
On Wed, 2019-02-13 at 04:41 -0700, PegoraroF10 wrote:
> Here is a SQL which will get that recovery mode. You can run it on
> any database because we created it with FROM VALUES, so ...
> But this one is that one which grows and grows memory use until all
> memory and swap space are g
*Here is a SQL which will get that recovery mode. You can run it on any
database because we created it with FROM VALUES, so ...*
But this one is that one which grows and grows memory use until all memory
and swap space are gone, so problem occurs. That other SQL which gives us
the same problem but
On Sun, Feb 10, 2019 at 03:15:38PM +1100, rob stone wrote:
> Down around line 87 onwards there are generate_series without any
> parameters, and further dubious usage of EPOCH, as well as DOW.
>
> Not having the table definitions is obviously clouding the analysis.
That seems like the root issue
Hi,
On Sat, 2019-02-09 at 15:46 -0600, Justin Pryzby wrote:
> Hi,
>
>
>
> "segfault" seems to mean you hit a bug, which we'll want more
> information to
> diagnose. Could you install debugging symbols ? Ubuntu calls their
> package
> postgresql-10-dbg or similar. And start server with coredu
Hi,
On Fri, Feb 08, 2019 at 02:11:33PM -0700, PegoraroF10 wrote:
> *Well, now we have two queries which stops completelly our postgres server.
> That problem occurs on 10.6 and 11.1 versions.
> On both server the problem is the same.
> Linux logs of old crash are:*
> Feb 1 18:39:53 fx-cloudserv
On 2/8/19 1:11 PM, PegoraroF10 wrote:
*Well, now we have two queries which stops completelly our postgres server.
That problem occurs on 10.6 and 11.1 versions.
On both server the problem is the same. *
*Linux Log of new crash, which takes several minutes to stop:*
Feb 8 15:06:40 fxReplicati
nsume more RAM and swap than the
server has available.
--
Jeremiah
From: PegoraroF10
Sent: Friday, February 8, 2019 4:11 PM
To: pgsql-gene...@postgresql.org
Subject: [EXTERNAL]Re: Server goes to Recovery Mode when run a SQL
CAUTION: This email originated from
*Well, now we have two queries which stops completelly our postgres server.
That problem occurs on 10.6 and 11.1 versions.
On both server the problem is the same.
Linux logs of old crash are:*
Feb 1 18:39:53 fx-cloudserver kernel: [ 502.405788] show_signal_msg: 5
callbacks suppressedFeb 1 18:39
Olá Marcos,
On Mon, 2019-02-04 at 08:33 -0700, PegoraroF10 wrote:
> About replication ... Logical Replication with CREATE
> PUBLICATION/SUBSCRIPTION.
>
> Yes, some DDL commands were ran on that server but none of them were
> related
> with that select.
> Let me explain better. We have a single se
On 2/4/19 7:33 AM, PegoraroF10 wrote:
About replication ... Logical Replication with CREATE
PUBLICATION/SUBSCRIPTION.
Yes, some DDL commands were ran on that server but none of them were related
with that select.
Let me explain better. We have a single server with a single database on it.
Each c
About replication ... Logical Replication with CREATE
PUBLICATION/SUBSCRIPTION.
Yes, some DDL commands were ran on that server but none of them were related
with that select.
Let me explain better. We have a single server with a single database on it.
Each customer has its own schema and connects
On 2/4/19 3:13 AM, PegoraroF10 wrote:
Nothing was change, Postgres 10, Ubuntu 16.04 and Schema was the same, before
and after that problem.
Well something changed or you would not be having a problem.
Well, that database is replicated and on replicated server that problem
doesn´t occur.
Def
Nothing was change, Postgres 10, Ubuntu 16.04 and Schema was the same, before
and after that problem.
Well, that database is replicated and on replicated server that problem
doesn´t occur.
--
Sent from: http://www.postgresql-archive.org/PostgreSQL-general-f1843780.html
Olá Marcos,
> My original query, which worked for some days and then went to
> recovery mode
> was ...
If it was working and then ceased to function, did any of the following
occur:-
1) Postgres version changed?
2) OS version changed?
3) Schema changes affecting the tables/views used in your q
On Sun, Feb 03, 2019 at 10:05:46AM -0800, Adrian Klaver wrote:
> On 2/3/19 8:32 AM, PegoraroF10 wrote:
>> I have a complex query which puts my server in recovery mode every time I
>> run it.
>> I don´t need to say that recovery mode is a situation you don´t want your
>> server goes to.
Do you mean
On 2/3/19 8:32 AM, PegoraroF10 wrote:
Just to be readable ...
And ... server log has only "the database system is in recovery mode" every
time I run that query.
I would assume that is in the log from the restart of the server after
it crashed and then restarted in recovery mode.
What is in
Just to be readable ...
And ... server log has only "the database system is in recovery mode" every
time I run that query.
I have a complex query which puts my server in recovery mode every time I
run it.
I don´t need to say that recovery mode is a situation you don´t want your
server goes to.
On 2/3/19 7:53 AM, PegoraroF10 wrote:
First the below is unreadable, probably because it is being sent through
Nabble. Please subscribe to list directly and try again. In meantime
could not tell from below, but what relevant information is in the logs
before and after?
I have a complex query
I´m using Postgres 10 on ubuntu in a Google VM (8 cores, 32Gb RAM, 250Gb SSD)
and DB has 70GB
--
Sent from: http://www.postgresql-archive.org/PostgreSQL-general-f1843780.html
I have a complex query which puts my server in recovery mode every time I run
it. I don´t need to say that recovery mode is a situation you don´t want
your server goes to.*If I´m using some subselects I´ll get that
situation*with StatusTrabalhando(Intkey) as (select Intkey from sys_Lookup
where Gr
36 matches
Mail list logo
