From: | "Simon Stiefel" <pgsqlml(at)nuclear-network(dot)com> |
---|---|
To: | <pgsql-general(at)postgresql(dot)org> |
Subject: | Question on database structure |
Date: | 2003-11-05 19:56:06 |
Message-ID: | 006801c3a3d6$da607830$1401a8c0@panic |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Hi people,
I want to migrate some old mysql-databases to postgresql.
With this step I want to optimize some database structures.
I have a (mysql-) database with all zip-codes and cities in germany.
As there are a lot of them I decided to split them in more tables at that time.
So now there are 10 tables with zip-codes (those starting with '0' in one table, those starting with '1' in another table, and so on).
I also have all streets of germany with their corresponding zip code.
Like the zip-code tables the streets are also splitted in 10 tables (same scheme as above).
My question now is, whether to keep that structure or to throw them together in two big tables?
For accessing that data it would be easier to make two tables, but I don't know what about performance (cause the street-table would have something about one million tuples)?
Thank you for your help!
Greetings,
Simon
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.3 (MingW32)
iD8DBQE/qVWAtbkSnV7uFrYRArUDAJ9DqzANtIkgEpms2p5GGt01T27BqwCgj3jn
1ljUP9Dxx9t1Hvmh/3VVWvY=
=v2x8
-----END PGP SIGNATURE-----
From | Date | Subject | |
---|---|---|---|
Next Message | George Essig | 2003-11-05 20:27:05 | tsearch2 and gist index bloat |
Previous Message | Lane Beneke | 2003-11-05 19:42:32 | Database Design & Application Server Design |