Re: [HACKERS] pgbench: Skipping the creating primary keys afterinitialization
| От | Fabien COELHO |
|---|---|
| Тема | Re: [HACKERS] pgbench: Skipping the creating primary keys afterinitialization |
| Дата | |
| Msg-id | alpine.DEB.2.20.1708031820090.16606@lancre обсуждение исходный текст |
| Ответ на | Re: [HACKERS] pgbench: Skipping the creating primary keys after initialization (Tom Lane <tgl@sss.pgh.pa.us>) |
| Ответы |
Re: [HACKERS] pgbench: Skipping the creating primary keys after initialization
|
| Список | pgsql-hackers |
>> For the CREATE stuff, the script language is SQL, the command to use it is >> "psql"... > >> The real and hard part is to fill tables with meaningful pseudo-random >> test data which do not violate constraints for any non trivial schema >> involving foreign keys and various unique constraints. > >> The solution for this is SQL for trivial cases, think of: >> "INSERT INTO Foo() SELECT ... FROM generate_series(...);" > > Yeah. I was also thinking that complicated data-generation requirements > could be handled with plpgsql DO blocks, avoiding the need for hard-wired > code inside pgbench. I do not thing that it is really be needed for what pgbench does, though. See attached attempt, including a no_foreign_keys option. The only tricky thing is to have the elapsed/remaining advancement report on stdout, maybe with some PL/pgSQL. Timings are very similar compared to "pgbench -i". -- Fabien. -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
Вложения
В списке pgsql-hackers по дате отправления: