News for hackers. Stuff that matters.
Re:Full text search in milliseconds with PostgreSQL by krastanov on Friday May 08, 2015 @01:20PM (#9512903)
Naive question from a person with little DB experience: Why store the metadata in JSON inside the database instead of in multiple columns in the same table? Is this not the point of using a database?
Re:Full text search in milliseconds with PostgreSQL by rietta on Friday May 08, 2015 @01:21PM (#9512914)
It's a form of 'document storage' that allows a application to store data without the need to account for everything in the database schema.
Re:Full text search in milliseconds with PostgreSQL by sitharus on Friday May 08, 2015 @04:08PM (#9513854)
It depends on what those columns are. For this case multiple columns are probably better, but if you're trying to search over multiple document types a JSON column could be more flexible.
Re:Full text search in milliseconds with PostgreSQL by devmach on Friday May 08, 2015 @03:40PM (#9513706)
If I'm not mistaken: Altering a table can be costly and may cause a performance issues, specially if you have millions of records. Rows will be most likely locked and get updated and during this process other threads should wait until related row become "free".
Re:Full text search in milliseconds with PostgreSQL by ddorian43 on Friday May 08, 2015 @04:02PM (#9513821)
That only happens if you add a non-nullable column.