News for hackers. Stuff that matters.
Re:Understanding Postgres Performance by krat0sprakhar on Tuesday October 02, 2012 @12:04PM (#4602662)
Slightly OT: I've been using MySQL for quite some time now and whenever I start a new project thinking that I'll use Postgres this time I find myself lazily opting for something that I know and going back to MySQL. Is there a Postgres guide that is concise, easy to follow and illustrates its advantages over other relational databases. The Postgres guide[1] is too sparse currently and the beginner Apress book[2] mentioned is 644 pages long.

1- http://www.postgresguide.com/

2 - http://www.amazon.com/gp/product/1590594789

Re:Understanding Postgres Performance by mattyb on Tuesday October 02, 2012 @12:32PM (#4602791)
The recently released 'PostgreSQL: Up and Running' may be right up your alley, at only 168 pages:

http://shop.oreilly.com/product/0636920025061.do

Re:Understanding Postgres Performance by atsaloli on Tuesday October 02, 2012 @01:52PM (#4603254)
http://www.wikivs.com/wiki/MySQL_vs_PostgreSQL MySQL vs PostgreSQL - an objective comparison
Re:Understanding Postgres Performance by craigkerstiens on Tuesday October 02, 2012 @12:15PM (#4602712)
What content would you like to see within Postgresguide?
Re:Understanding Postgres Performance by jcampbell1 on Tuesday October 02, 2012 @12:38PM (#4602832)
Probably a good idea to add a bit about serial, and sequences. This tends to confuse mysql people like myself.

I for instance don't know what happens when I copy or dump and restore a postgres table that relies on a sequence. Mysql auto-magically takes care of it by saving the next auto increment id in table dump or copy.

Re:Understanding Postgres Performance by joevandyk on Tuesday October 02, 2012 @12:55PM (#4602936)
If you use pg_dump to dump/restore the table, it will reset the sequence to the correct value. Look at the dump file, there will be a setval of the sequence.
Re:Understanding Postgres Performance by jeltz on Tuesday October 02, 2012 @01:41PM (#4603194)
Agreed, especially since sequences is a more powerful tool with a wider use than auto increment. For example you can use the same sequence for multiple tables, or use them without being connected to any table.