Duplicate and reappearing tables.
Hi all I am running a currently roughly 400G-sized single Monet instance. We load daily CSV files into corresponding tables, and use merge tables to query the data (e.g., feed_20160301, feed_20160302, ... and feed_mt). We have a problem mainly with duplicate tables (same schema + table name, different table_id in sys.tables). My approach is to "DROP TABLE foo" for N - 1 times if there are N copies (is there even a way to SELECT or DROP by table_id?). This seemingly fixes the problem, however after restarting the database, the dropped tables reappear. Similarly, I have some old empty tables, which reappear after being dropped when the database is restarted. We start and stop the database to roll over connections during maintenance. Is this a known issue? Can it be fixed? Not sure how to make this reproducible. Thanks, Nicolas Stalder.
Hi Nicolas, could you please share which version of MonetDB you're using on which OS? Also, did you initially create your database with the very same version of MonetDB that you're using now, or did you create it with an earlier version (which) and then upgrade it to the one you're using now (directly or via intermetiate release steps)? Thanks! Stefan ----- On Mar 15, 2016, at 7:56 PM, Nicolas Stalder n+monet@stalder.io wrote:
Hi all
I am running a currently roughly 400G-sized single Monet instance. We load daily CSV files into corresponding tables, and use merge tables to query the data (e.g., feed_20160301, feed_20160302, ... and feed_mt).
We have a problem mainly with duplicate tables (same schema + table name, different table_id in sys.tables). My approach is to "DROP TABLE foo" for N - 1 times if there are N copies (is there even a way to SELECT or DROP by table_id?). This seemingly fixes the problem, however after restarting the database, the dropped tables reappear. Similarly, I have some old empty tables, which reappear after being dropped when the database is restarted. We start and stop the database to roll over connections during maintenance.
Is this a known issue? Can it be fixed? Not sure how to make this reproducible.
Thanks, Nicolas Stalder.
_______________________________________________ users-list mailing list users-list@monetdb.org https://www.monetdb.org/mailman/listinfo/users-list
-- | Stefan.Manegold@CWI.nl | DB Architectures (DA) | | www.CWI.nl/~manegold/ | Science Park 123 (L321) | | +31 (0)20 592-4212 | 1098 XG Amsterdam (NL) |
Hi Nicolas, We have (and unfortunately sometimes still do) experience similar issues. The issues appear most often at stopping and starting the database. In an earlier thread (named "WAL read files") Pierre-Adrien found out that underscores in table and/or column names could cause conflicts, and cause similar issues. Maybe this is related to the issue you are experiencing? See also the bug report: https://www.monetdb.org/bugzilla/show_bug.cgi?id=3912 Regards, Marcel Blok -----Oorspronkelijk bericht----- Van: users-list [mailto:users-list-bounces+m.blok=chs.nl@monetdb.org] Namens Stefan Manegold Verzonden: dinsdag 15 maart 2016 21:27 Aan: Communication channel for MonetDB users Onderwerp: Re: Duplicate and reappearing tables. Hi Nicolas, could you please share which version of MonetDB you're using on which OS? Also, did you initially create your database with the very same version of MonetDB that you're using now, or did you create it with an earlier version (which) and then upgrade it to the one you're using now (directly or via intermetiate release steps)? Thanks! Stefan ----- On Mar 15, 2016, at 7:56 PM, Nicolas Stalder n+monet@stalder.io wrote:
Hi all
I am running a currently roughly 400G-sized single Monet instance. We load daily CSV files into corresponding tables, and use merge tables to query the data (e.g., feed_20160301, feed_20160302, ... and feed_mt).
We have a problem mainly with duplicate tables (same schema + table name, different table_id in sys.tables). My approach is to "DROP TABLE foo" for N - 1 times if there are N copies (is there even a way to SELECT or DROP by table_id?). This seemingly fixes the problem, however after restarting the database, the dropped tables reappear. Similarly, I have some old empty tables, which reappear after being dropped when the database is restarted. We start and stop the database to roll over connections during maintenance.
Is this a known issue? Can it be fixed? Not sure how to make this reproducible.
Thanks, Nicolas Stalder.
_______________________________________________ users-list mailing list users-list@monetdb.org https://www.monetdb.org/mailman/listinfo/users-list
-- | Stefan.Manegold@CWI.nl | DB Architectures (DA) | | www.CWI.nl/~manegold/ | Science Park 123 (L321) | | +31 (0)20 592-4212 | 1098 XG Amsterdam (NL) | _______________________________________________ users-list mailing list users-list@monetdb.org https://www.monetdb.org/mailman/listinfo/users-list
participants (3)
-
Marcel Blok -
Nicolas Stalder -
Stefan Manegold