Heikki Linnakangas e999f66b01 Use a cached WaitEventSet instead of WaitLatchOrSocket. ...

When we repeatedly wait for the same events, it's faster to create the
event set once and reuse it. While testing with a sequential scan test
case, I saw WaitLatchOrSocket consuming a lot of CPU:

> -   40.52%     0.14%  postgres  postgres           [.] WaitLatchOrSocket
>    - 40.38% WaitLatchOrSocket
>       + 17.83% AddWaitEventToSet
>       + 9.47% close@plt
>       + 8.29% CreateWaitEventSet
>       + 4.57% WaitEventSetWait

This eliminates most of that overhead.

2022-11-08 19:45:14 +02:00

..

neon

Use a cached WaitEventSet instead of WaitLatchOrSocket.

2022-11-08 19:45:14 +02:00

neon_test_utils

Rename old project name references

2022-09-14 08:14:05 +03:00

neon_walredo

Move walredo process code under pgxn in the main 'neon' repository.

2022-10-31 01:11:50 +01:00

typedefs.list

Refotmat pgxn code, add typedefs.list that was used

2022-09-14 08:14:05 +03:00