Comments (6)
laurenz
commented on September 28, 2024
I see the same thing when testing here with PostgreSQL v15.
I haven't looked at the regression tests in a long time, perhaps they have rotted.
Could you test if pgreplay works for you? It would be interesting to know if there is a real problem or if only the tests need attention.
from pgreplay.
laurentmmeyer
commented on September 28, 2024
- So I run the tests on 12 too and got stuck at the same point.
- However, I followed you advice and gave the software a go.
I have a rather simple logfile:
2022-06-18 19:17:16.075 CEST|||62ae089c.61d3|LOG: starting PostgreSQL 12.11 (Ubuntu 12.11-0ubuntu0.20.04.1) on x86_64-pc-linux-gnu, compiled by gcc (Ubuntu 9.4.0-1ubuntu1~20.04.1) 9.4.0, 64-bit
2022-06-18 19:17:16.075 CEST|||62ae089c.61d3|LOG: listening on IPv4 address "127.0.0.1", port 5432
2022-06-18 19:17:16.076 CEST|||62ae089c.61d3|LOG: listening on Unix socket "/var/run/postgresql/.s.PGSQL.5432"
2022-06-18 19:17:16.087 CEST|||62ae089c.61d5|LOG: database system was shut down at 2022-06-18 19:17:15 CEST
2022-06-18 19:17:16.092 CEST|||62ae089c.61d3|LOG: database system is ready to accept connections
2022-06-18 19:17:16.665 CEST|[unknown]|[unknown]|62ae089c.61dc|LOG: connection received: host=[local]
2022-06-18 19:17:17.173 CEST|[unknown]|[unknown]|62ae089d.61df|LOG: connection received: host=[local]
2022-06-18 19:17:17.173 CEST|postgres|template1|62ae089d.61df|LOG: connection authorized: user=postgres database=template1 application_name=psql
2022-06-18 19:17:17.177 CEST|postgres|template1|62ae089d.61df|LOG: statement:
2022-06-18 19:17:17.177 CEST|postgres|template1|62ae089d.61df|LOG: disconnection: session time: 0:00:00.004 user=postgres database=template1 host=[local]
2022-06-18 19:17:17.687 CEST|[unknown]|[unknown]|62ae089d.61e2|LOG: connection received: host=[local]
2022-06-18 19:17:17.688 CEST|postgres|template1|62ae089d.61e2|LOG: connection authorized: user=postgres database=template1 application_name=psql
2022-06-18 19:17:17.688 CEST|postgres|template1|62ae089d.61e2|LOG: statement:
2022-06-18 19:17:17.689 CEST|postgres|template1|62ae089d.61e2|LOG: disconnection: session time: 0:00:00.001 user=postgres database=template1 host=[local]
2022-06-18 19:17:18.198 CEST|[unknown]|[unknown]|62ae089e.61e5|LOG: connection received: host=[local]
2022-06-18 19:17:18.199 CEST|postgres|template1|62ae089e.61e5|LOG: connection authorized: user=postgres database=template1 application_name=psql
2022-06-18 19:17:18.200 CEST|postgres|template1|62ae089e.61e5|LOG: statement:
2022-06-18 19:17:18.200 CEST|postgres|template1|62ae089e.61e5|LOG: disconnection: session time: 0:00:00.001 user=postgres database=template1 host=[local]
2022-06-18 19:17:34.595 CEST|[unknown]|[unknown]|62ae08ae.61f2|LOG: connection received: host=[local]
2022-06-18 19:17:34.596 CEST|postgres|postgres|62ae08ae.61f2|LOG: connection authorized: user=postgres database=postgres application_name=psql
2022-06-18 19:18:01.058 CEST|postgres|postgres|62ae08ae.61f2|LOG: statement: SELECT pg_catalog.quote_ident(datname) FROM pg_catalog.pg_database WHERE substring(pg_catalog.quote_ident(datname),1,2)='po'
LIMIT 1000
2022-06-18 19:18:01.593 CEST|[unknown]|[unknown]|62ae08c9.6614|LOG: connection received: host=[local]
2022-06-18 19:18:01.594 CEST|postgres|postgres|62ae08c9.6614|LOG: connection authorized: user=postgres database=postgres application_name=psql
2022-06-18 19:18:01.595 CEST|postgres|postgres|62ae08ae.61f2|LOG: disconnection: session time: 0:00:26.999 user=postgres database=postgres host=[local]
2022-06-18 19:18:06.539 CEST|postgres|postgres|62ae08c9.6614|LOG: statement: CREATE TABLE CUSTOMERS(
ID INT NOT NULL,
NAME VARCHAR (20) NOT NULL,
AGE INT NOT NULL,
ADDRESS CHAR (25) ,
SALARY DECIMAL (18, 2),
PRIMARY KEY (ID)
);
2022-06-18 19:18:19.308 CEST|postgres|postgres|62ae08c9.6614|LOG: statement: INSERT INTO CUSTOMERS (ID,NAME,AGE,ADDRESS,SALARY)
VALUES (1, 'Ramesh', 32, 'Ahmedabad', 2000.00 );
2022-06-18 19:18:19.310 CEST|postgres|postgres|62ae08c9.6614|LOG: statement: INSERT INTO CUSTOMERS (ID,NAME,AGE,ADDRESS,SALARY)
VALUES (2, 'Khilan', 25, 'Delhi', 1500.00 );
2022-06-18 19:18:19.312 CEST|postgres|postgres|62ae08c9.6614|LOG: statement: INSERT INTO CUSTOMERS (ID,NAME,AGE,ADDRESS,SALARY)
VALUES (3, 'kaushik', 23, 'Kota', 2000.00 );
2022-06-18 19:18:19.313 CEST|postgres|postgres|62ae08c9.6614|LOG: statement: INSERT INTO CUSTOMERS (ID,NAME,AGE,ADDRESS,SALARY)
VALUES (4, 'Chaitali', 25, 'Mumbai', 6500.00 );
2022-06-18 19:18:19.315 CEST|postgres|postgres|62ae08c9.6614|LOG: statement: INSERT INTO CUSTOMERS (ID,NAME,AGE,ADDRESS,SALARY)
VALUES (5, 'Hardik', 27, 'Bhopal', 8500.00 );
2022-06-18 19:18:20.474 CEST|postgres|postgres|62ae08c9.6614|LOG: statement: INSERT INTO CUSTOMERS (ID,NAME,AGE,ADDRESS,SALARY)
VALUES (6, 'Komal', 22, 'MP', 4500.00 );
2022-06-18 19:18:30.222 CEST|postgres|postgres|62ae08c9.6614|LOG: statement: INSERT INTO CUSTOMERS
VALUES (7, 'Muffy', 24, 'Indore', 10000.00 );
2022-06-18 19:18:38.918 CEST|postgres|postgres|62ae08c9.6614|LOG: statement: SELECT ID, NAME, SALARY FROM CUSTOMERS;
2022-06-18 19:18:47.579 CEST|postgres|postgres|62ae08c9.6614|LOG: statement: SELECT * FROM CUSTOMERS;
and when I try to replay it; I get the following (I created the target replayed db beforehand):
Parse statistics
================
Log lines read: 49
Total SQL statements processed: 0
Simple SQL statements processed: 0
Parametrized SQL statements processed: 0
Named prepared SQL statements executions processed: 0
Cancel requests processed: 0
Fast-path function calls ignored: 0
Duration of recorded workload: 0.000 seconds
Replay statistics
=================
Speed factor for replay: 1.000
Total run time: 0.000 seconds
Maximum lag behind schedule: 0 seconds
Calls to the server: 0
(0.000 calls per second)
Total number of connections: 0
Maximum number of concurrent connections: 0
Average number of concurrent connections: 0.000
SQL statements executed: 0
It is not really what I expected; did I miss something?
from pgreplay.
laurenz
commented on September 28, 2024
Strange. When I copy & paste your logfile from above, it works for me:
Parse statistics
================
Log lines read: 49
Total SQL statements processed: 11
Simple SQL statements processed: 11
Parametrized SQL statements processed: 0
Named prepared SQL statements executions processed: 0
Cancel requests processed: 0
Fast-path function calls ignored: 0
Duration of recorded workload: 1 minutes 30.406 seconds
I called pgreplay like this:
pgreplay -j <logfilename>and it replayed the statements against my postgres database.
from pgreplay.
laurenz
commented on September 28, 2024
About the tests, they certainly need to be revisited and fixed. But that is not a very high priority for me at this point.
from pgreplay.
TsinghuaLucky912
commented on September 28, 2024
Hello, I did a regression test on pg15.1 and found a problem: I guess it may be related to the process (role) of playing back data files. I rolled back pg to 12.0 and there is still a new problem: about session id
I would like to ask which pg version can perfectly pass the regression test of pgreplay?
from pgreplay.
laurenz
commented on September 28, 2024
I finally got around to fixing this problem.
The cause for the error was that the regression tests need login roles postgres and hansi, but I discovered another problem along the way.
I have improved the documentation for the regression tests.
from pgreplay.
Related Issues (20)
- make install fails on Mac OS X HOT 5
- Unable to compile pgreplay on ubuntu 18.04 HOT 2
- pgreplay seems to have stopped suddenly when executing HOT 10
- Generating undo records by using pgreplay HOT 1
- pgreplay not working with RDS csvlog HOT 2
- Queries per second HOT 3
- Replay freezes, all queries stuck in ClientRead state. HOT 3
- replay and uuids HOT 1
- Will the program support pg11 onward? HOT 3
- Transaction Deadlocks on Replay HOT 7
- Invalid free on replaying server-side prepare "ROLLBACK; DEALLOCATE ALL". HOT 4
- First run always lags behind HOT 3
- connection to database failed for a specific session HOT 1
- Parsing line error HOT 12
- Upgrade from pg 12 to pg 14 HOT 2
- ./configure fails on pg15.0 HOT 2
- Opened connections HOT 2
- Will PQgetResult cause stat_stmt statistics errors? HOT 1
- docker build Fails with Error (from master, commit a2f7c113197ed5623b35f09bfc299aae971d56e8) HOT 2
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from pgreplay.