database-partitioning

Excuse me for my english. I have 2 tables, both partitioned by date interval, but on different fields. There is a big amount of records in both tables(~100kk in each partition). First table keep it's 3 last(by date) partitions in fast discks tablespace, others partitions is in slow discks tablespace. Also I have some system, which processing data. It execute processes in parallel, each one get data from first table by select statement and put processed data into second table. So I need select data from first table only from "fast"(!) partitions to put it in second table. But second table

I am trying to make a self-managing partition table setup with Postgres. It all revolves around this function but I can't seem to get Postgres to accept my table names. Any ideas or examples of self-managing partition table trigger functions? My current function: DECLARE day integer; year integer; tablename text; startdate text; enddate text; BEGIN day:=date_part('doy',to_timestamp(NEW.date)); year:=date_part('year',to_timestamp(NEW.date)); tablename:='pings_'||year||'_'||day||'_'||NEW.id; -- RAISE EXCEPTION 'tablename=%',tablename; PERFORM 'tablename' FROM pg_tables WHERE 'schemaname'

I understand that as of MySQL 5.5, you can now partition a table by non-integer values like a varchar. I have a table where I perform a lot of lookups on a single varchar column, hence I would like to partition on that for performance reasons. In all instances, the value of the column is a single alphabetical word (strictly lower case a-z, enforced by validation). What I would like to do is partition this table by the first letter in each word stored, so all words beginning with 'a' go in the first partition, 'b' in the second etc. My gut feeling is that I could probably construct the create

I'm currently trying to improve the speed of SELECTS for a MySQL table and would appreciate any suggestions on ways to improve it. We have over 300 million records in the table and the table has the structure tag, date, value. The primary key is a combined key of tag and date. The table contains information for about 600 unique tags most containing an average of about 400,000 rows but can range from 2000 to over 11 million rows. The queries run against the table are: SELECT date, value FROM table WHERE tag = "a" AND date BETWEEN 'x' and 'y' ORDER BY date ....and there are very few if any

I am aware of the cursor object in Django. Is there any other preferred way to execute raw SQL in migrations? I want to introduce postgresql partitioning for one of my models tables. The partition logic is a bunch of functions and triggers that have to be added to the database on setup which I'd like to automate. One way: The best way I found to do this is using RunSQL: Migrations contains the RunSQL class. To do this: ./manage.py makemigrations --empty myApp edit the created migrations file to include: operations = [ migrations.RunSQL('RAW SQL CODE') ] As Nathaniel Knight mentioned, RunSQL