New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Is enable_wal needed in standby server? #144
Comments
Does it mean that you can do full text search with PGroonga index on standby server with If it's yes, could you show
How did you calculate the DB size on the master server and the standby server? You can't calculate the DB size for PGroonga with the standard PostgreSQL way. See also: #15
Yes. |
yes, explain on the standby server(pg12) is show pgroonga.enable_wal; -- off, on both master/slave
explain select * from "data-xxx"
where extra &` 'string @ "121号楼"'; Index Scan using "data-xxx_extra_idx" on "data-xxx" (cost=0.00..8196.64 rows=206 width=1687)
Index Cond: (extra &` 'string @ "121号楼"'::text) same as master for the size , I did # master, around 3.7k files under 16386
5.4G /xxx/base/16386
18M /xxx/base/26334
8.0M /xxx/base/1
5.5G /xxx/base
# slave, around 6k files under 16386
17G /xxx/base/16386
17G /xxx/base I will do a file list diff on it later |
It's strange... Do you use streaming replication https://pgroonga.github.io/reference/streaming-replication.html or logical replication https://pgroonga.github.io/reference/logical-replication.html ? |
I use repmgr, it shall be streaming replica is it because the index exists before I did the first base backup? let me double check with new created table. |
I tried the if I add the without a restart of master, I added |
Does it mean that you added If you used You don't need to re-run base backup after you enable |
Finally got a low traffic chance to restart the server, it seems not working, I still got the error.from the log I can see each time recreate/ reindex it does switch the object xxx | 2020-07-18 06:39:03.992 UTC [97] STATEMENT: SELECT title FROM entries WHERE title %% 'replication';
xxx | 2020-07-18 06:39:05.405 UTC [97] ERROR: pgroonga: object isn't found: <Sources69233>
xxx | 2020-07-18 06:39:05.405 UTC [97] STATEMENT: SELECT title FROM entries WHERE title %% 'replication';
xxx | 2020-07-18 06:40:14.643 UTC [97] ERROR: pgroonga: object isn't found: <Sources69234>
xxx | 2020-07-18 06:40:14.643 UTC [97] STATEMENT: SELECT title FROM entries WHERE title %% 'replication';
xxx | 2020-07-18 06:40:17.660 UTC [97] ERROR: pgroonga: object isn't found: <Sources69234>
xxx | 2020-07-18 06:40:17.660 UTC [97] STATEMENT: SELECT title FROM entries WHERE title %% 'replication';
xxx | 2020-07-18 06:41:57.280 UTC [97] ERROR: pgroonga: object isn't found: <Sources69235>
xxxx | 2020-07-18 06:41:57.280 UTC [97] STATEMENT: SELECT title FROM entries WHERE title %% 'replication';
xxx | 2020-07-18 06:41:58.789 UTC [97] ERROR: pgroonga: object isn't found: <Sources69235>
xxx | 2020-07-18 06:41:58.789 UTC [97] STATEMENT: SELECT title FROM entries WHERE title %% 'replication'; |
Um... |
I tried to reproduce it using the docker images with fresh database...and it works... so I wonder would it be possible that my production master was created using since the database is not that large, I would try later just dump and restore to a new database to see if it's ok |
here is a repo reproducing the case |
@zyp-rgb Thanks. We found that postgresql-12-pgroonga package isn't build with WAL support. Could you update your Docker image and try again? |
That would work!! |
Thanks for confirming this. |
Hi,
I'm making a slave db and found this parameter in the document.
without it, the streaming seems to be ok, but strange that the slave db size is about 2x of the master(investigating)
my question is, is it required for slave db to maintain a usable pgroonga index?
The text was updated successfully, but these errors were encountered: