189 reputation
4
bio website
location
age 30
visits member for 1 year, 11 months
seen Jul 21 at 18:53

Jul
14
awarded  Popular Question
May
2
answered Primary key within JSON data in Postgresql
May
2
accepted Primary key within JSON data in Postgresql
May
2
comment Primary key within JSON data in Postgresql
Thanks for the edit, I just wanted to be sure I was understanding! R.e. why: Up until a few hours ago I'd always assumed that a specifying unique on an index was just a hint to the DB that the values were unique, but if you wanted uniqueness enforced you needed an explicit constraint. As I now understand it, they're just two sides of the same coin, per this question :)
May
1
comment Primary key within JSON data in Postgresql
Thanks. In your answer you say, "You can have a UNIQUE constraint", do you just mean 'in general', then? I got excited reading that because I thought you meant "You can have a UNIQUE constraint"...on an expression index.
May
1
comment Primary key within JSON data in Postgresql
Can you cite any docs for this? I couldn't find any. Also, do you think I should be able to ADD CONSTRAINT t_unique_id UNIQUE as shown in my second example?
May
1
asked Primary key within JSON data in Postgresql
Feb
22
comment Does updating a partially indexed field add or remove it from an index in Postgres
Updated gist link to IRC conversation
Oct
25
comment Does updating a partially indexed field add or remove it from an index in Postgres
Here's a cleaned version of the IRC conversation referenced above. It was from the #postgresql channel on the freenode IRC network, there are very helpful people in there! (also updated my name on here to match my IRC handle, to avoid confusion).
Oct
25
accepted Does updating a partially indexed field add or remove it from an index in Postgres
Oct
25
comment Does updating a partially indexed field add or remove it from an index in Postgres
Thanks for the great answer, I'm a reluctant to accept right now though, because I've put this live and am still seeing the index still grow, despite the number of archived = false rows remaining (essentially) constant (including after a VACUUM, but not a FULL)
Oct
13
comment How should we handle rows which won't be queried once they are old in PostgreSQL?
Thank you for the comprehensive response and ideas. More karma up for grabs on a follow-up question.
Oct
13
asked Does updating a partially indexed field add or remove it from an index in Postgres
Oct
13
accepted PostgreSQL Index Caching
Oct
5
asked PostgreSQL Index Caching
Oct
5
awarded  Scholar
Oct
5
accepted How should we handle rows which won't be queried once they are old in PostgreSQL?
Oct
5
awarded  Supporter
Sep
29
awarded  Student
Sep
28
asked How should we handle rows which won't be queried once they are old in PostgreSQL?