network profile
| bio | website | depesz.com |
|---|---|---|
| location | ||
| age | 36 | |
| visits | member for | 2 years, 1 month |
| seen | Jun 15 at 12:36 | |
| stats | profile views | 56 |
|
Apr 27 |
awarded | Yearling |
|
Feb 14 |
comment |
Safe way to stop/abort REINDEX Not that I know of, but since it's just two commands, you can write the commands in "recreate.sql" file, and now you have a script. |
|
Feb 14 |
answered | Safe way to stop/abort REINDEX |
|
Feb 8 |
answered | INSERT trigger dying with with #target columns not equal to #expressions, but they are equal |
|
Feb 8 |
comment |
I accidentally set password to blank for a PostgreSQL database, how do I change it? No problem at all. I definitely do not feel special, I'm just not in favor of adding yet-another (after all google/bing/whatever caches) copy of the same information. But if someone (like you in this case) wants to add it - I have no problem with it. |
|
Feb 7 |
awarded | Commentator |
|
Feb 6 |
answered | I accidentally set password to blank for a PostgreSQL database, how do I change it? |
|
Jul 14 |
comment |
Most efficient way to add a serial column to a huge table @ThiDuongNguyen: and is there no combination of columns that should be unique? |
|
Jul 14 |
comment |
Most efficient way to add a serial column to a huge table Setting multiple times is not problematic. Gaps - well, sure, but then you can at the very end, add one more sanity-check update, like: update foo set bar = nextval('foo_bar_seq') where bar is null; |
|
Jul 13 |
comment |
Most efficient way to add a serial column to a huge table @Erwin: I find it hard to see how's that relevant. I mean - sure, concurrent update can set bar to some other value. And? |
|
Jul 13 |
comment |
Most efficient way to add a serial column to a huge table "Stable"? Update will not guarantee any order. |
|
Jul 13 |
answered | Most efficient way to add a serial column to a huge table |
|
Jul 3 |
answered | Postgres - Create table with foreign key constraint too slow |
|
May 7 |
answered | Why is pg_dumpall throwing an "OID does not exist'' error? |
|
Apr 27 |
awarded | Yearling |
|
Apr 10 |
answered | send jobs via psql asynchronously |
|
Apr 9 |
answered | pg_relation_size does not show any difference after VACUUM ANALYZE |
|
Apr 5 |
answered | Initial recovery Postgres with backup in sync commit mode |
|
Mar 27 |
comment |
Postgres full text search with multiple columns, why concat in index and not at runtime? @jcolebrand Based on timestamps at these posts - it looks that it sorts based on when given post was edited, and not when it was created. |
|
Mar 26 |
answered | Postgres synchronized backup - what's with the archive? |
