Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Allow merging channels #4

Open
zopieux opened this issue Oct 3, 2021 · 0 comments
Open

Allow merging channels #4

zopieux opened this issue Oct 3, 2021 · 0 comments

Comments

@zopieux
Copy link
Owner

zopieux commented Oct 3, 2021

That is to say, treat multiple channels as one. Particularly useful when crypto dumbfucks decide to take over a well-established IRC server, triggering a massive migration to a new one. As someone browsing the logs, the migration should be transparent.

This could be done using a config value that maps 1+ channels to one, eg.

aliases = {
  "libera/#foo" = ["obsolete/#foo", "superold/#f00"],
}
zopieux added a commit that referenced this issue Oct 5, 2021
@zopieux
Implement channel merging.
318cb43 
This is a non-destructive fix for issue #4, but performance is terrible.

Sadly, using `channel = ANY(…)` brings Postgres to its knees because it
stops using its index. Maybe we could try unrolling into an OR list
manually, see if that helps.
zopieux added a commit that referenced this issue Oct 5, 2021
@zopieux
Implement channel merging.
c0f88c6 
This is a non-destructive fix for issue #4, but performance is terrible.

Sadly, using `channel = ANY(…)` brings Postgres to its knees because it
stops using its index. Maybe we could try unrolling into an OR list
manually, see if that helps.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@zopieux