Hi!
To me the relevant part of the log is below. Not sure what it means though:
[3604-0.187] execute.c[Exec_with_parameters_resolved]444:
stmt_with_params = ';SELECT * FROM temptulemus offset 0 limit 900'
[3604-0.187] execute.c[Exec_with_parameters_resolved]449: about to begin
SC_execute
I would like to get suggestions and feedback on aws sct/dms vs ora2pg for
an Oracle (on-prem) to PostgreSQL (aws rds) migration project.
One big difference between them I see is the fact that dms supports
incremental loads from oracle to postgres (dont think ora2pg supports that,
but I could be
On 2/21/20 2:02 PM, Andrus wrote:
Please reply to list also.
Ccing list.
To me the relevant part of the log is below. Not sure what it means though:
[3604-0.187] execute.c[Exec_with_parameters_resolved]421: copying
statement params: trans_status=1, len=45, stmt=';SELECT * FROM
temptulemus
Mark Fletcher writes:
> Running 9.6.15, this morning we got a 'shared buffer hash table corrupted'
> error on a query. I reran the query a couple hours later, and it completed
> without error. This is running in production on a Linode instance which
> hasn't seen any config changes in months.
>
Hi All,
Running 9.6.15, this morning we got a 'shared buffer hash table corrupted'
error on a query. I reran the query a couple hours later, and it completed
without error. This is running in production on a Linode instance which
hasn't seen any config changes in months.
I didn't find much
Hi!
Alright so what does:
\d temptulemus
Did not find any relation named "temptulemus".
and/or
\d andmetp
Table "public.andmetp"
Column | Type | Collation | Nullable | Default
+---+---+--+-
andmetp|
On 2/21/20 12:50 PM, Andrus wrote:
Hi!
In psql what does \d tempestuous show?
What relation is andmetp to tempestuous?
I'm sorry, this was typo. Correct commands issued from application are
select drop_table('temptulemus');
create temp table temptulemus as select * from andmetp;
select *
Hi!
In psql what does \d tempestuous show?
What relation is andmetp to tempestuous?
I'm sorry, this was typo. Correct commands issued from application are
select drop_table('temptulemus');
create temp table temptulemus as select * from andmetp;
select * from temptulemus offset 0 limit 900;
On 2/21/20 9:55 AM, Albrecht Dreß wrote:
Am 20.02.20 21:41 schrieb(en) Adrian Klaver:
It would be nice to know what:
[snip]
represented in:
Dropping and re-creating the function is actually the last operation in
the script. The function is /very/ simple (just a wrapper to hide all
I am very interested in this discussion. We settled a table with a single
timestamp field that a script updates every minute with NOW() so that we
can check the timestamp of that table on the replica, assuming the clocks
are synced, then we will be able to compute the lag.
On 2/21/20 10:24 AM, Andrus wrote:
Hi!
forgot to say publish the Linux logs it may have more details what is
going on
Linux server has older application client which replicates all data one
from andmetp table using select * from andmetp
I tried several times. Linux log contains
2020-02-21
Hi!
Yes publish the ODBC logs
I send psqlodbc log from windows server to you.
I added and removed Debug=1 parameter from odbc conncetion string, ran
application as administrator.
Other errors
2020-02-21 21:27:30 EET ERROR: invalid memory alloc request size
4294967293
2020-02-21
Yes publish the ODBC logs
seeing the Linux logs tells us the ODBC client crashing NOT the client
process. if the linux postgrsql client process crashes it typically will
cause the postgresql postmaster to panic and restart as it has to assume
it corrupt share memory.
On Fri, Feb 21, 2020 at
Hi!
forgot to say publish the Linux logs it may have more details what is going
on
Linux server has older application client which replicates all data one from
andmetp table using select * from andmetp
I tried several times. Linux log contains
2020-02-21 16:18:50 EET mydbadmin mydb
Am 20.02.20 21:41 schrieb(en) Adrian Klaver:
It would be nice to know what:
[snip]
represented in:
Dropping and re-creating the function is actually the last operation in the script. The
function is /very/ simple (just a wrapper to hide all internals from "agent"
clients):
forgot to say publish the Linux logs it may have more details what is going
on
On Fri, Feb 21, 2020 at 12:27 PM Justin wrote:
> is this happening from any client or just a specific client running ODBC?
> are the clients running AV if so are the AV versions the same?
>
> Given this is killing a
is this happening from any client or just a specific client running ODBC?
are the clients running AV if so are the AV versions the same?
Given this is killing a Linux server, sounds like ODBC is sending back
garabage data to the server crashing it.
There are several settings in OBDC, to change
Hi!
Realized I should have been clearer. By pre-libpq I meant this:
https://odbc.postgresql.org/docs/release.html
psqlODBC 09.05.0100 Release
Changes:
Use libpq for all communication with the server
Previously, libpq was only used for authentication. Using it for all
communication lets
Hello!
I currently use Slony for replication and want to switch to logical
replication. With Slony I was aware of the replication lag of each slave
in seconds. This info was available regardless if a slave was online or
offline.
For my application I need to know the "delay" of all replicas,
On Friday, February 21, 2020, stan wrote:
>
> How can I get the name of the table that fired a trigger, in the function
> called by that trigger?
>
Language specific. Read the language docs. For pl/pgsql:
https://www.postgresql.org/docs/12/plpgsql-trigger.html
David J.
On Fri, Feb 21, 2020 at 12:48 PM Daulat Ram
wrote:
> What are the differences between Oracle and Postgres tablespace.
>
> I hope this[1] wiki page will help you.
> Can we assign tablespace during Postgres schema creation . As I know in
> Oracle we assign the tablespace during user/schema
Hi!
I'm seeing varying number of rows removed by filter on a parallel append
query:
CREATE TABLE usuario (
id bigint generated always as identity,
nome text
);
INSERT INTO usuario (nome)
SELECT md5(seq)::text
FROM generate_series(1,50,1) tab(seq);
ANALYZE usuario;
EXPLAIN
How can I get the name of the table that fired a trigger, in the function
called by that trigger?
--
"They that would give up essential liberty for temporary safety deserve
neither liberty nor safety."
-- Benjamin Franklin
23 matches
Mail list logo
