Recently someone was looking for help with script from Pg wiki. I never really checked it, but when talking with the guy needing help, I looked at it. And didn’t really like it.
Some people are afraid of triggers. Reasons for this are not really understandable for me, but I guess it stems from the fact that these are usually application developers, and not database admins. Or they encountered some kind of problem with triggers, and now they tend to think that triggers are inherently evil. But they … Continue reading “How I Learned to Stop Worrying and Love the Triggers”
On 25th of January, Tom Lane committed patch: Implement ALTER TABLE ADD UNIQUE/PRIMARY KEY USING INDEX. This feature allows a unique or pkey constraint to be created using an already-existing unique index. While the constraint isn’t very functionally different from the bare index, it’s nice to be able to do that for documentation purposes. … Continue reading “Waiting for 9.1 – Add UNIQUE/PRIMARY KEY with index”
Starting new blog series – explanation of various configuration parameters. I will of course follow no schedule or order – if I’d had to – it would be my job, and in this way – it’s fun. First configuration parameter to write about is checkpoint_completion_target.
Every now and then there is someone on IRC, mailing lists, or private contact which asks about rules. My answer virtually always is: don’t use rules. If you think that they solve your problem, think again. Why?
as most of you know postgresql can easily speedup searches using: field like ‘something%’ and (less easily): field like ‘%something’ but how about: field like ‘%something%’ general idea is to use some kind of full text search/indexing – tsearch, lucene, sphinx, you name it. but sometimes you can’t install fts/fti, or it doesn’t really solve … Continue reading “speeding up like ‘%xxx%’”
just recently i saw a very interesting situation. one table in customer database (with about 1.5 milion rows) was *very often* updated. using series of simple: update table set field = .., where id = … updates always updated 1 record, search was using primary key, so it was quite fast. what was strange was … Continue reading “avoiding “empty” updates”