network profile
| bio | website | |
|---|---|---|
| location | ||
| age | 33 | |
| visits | member for | 6 months |
| seen | 23 hours ago | |
| stats | profile views | 1 |
I believe that technology can get us out of this mess we're in. It's the last, best hope.
|
Mar 4 |
comment |
“custom archiver out of memory” error when restoring large DB using pg_restore This problem was fixed with another dump, which, coupled with the "extra data" messages, suggests that the original one was corrupt. The "out of memory" message was a red herring. Thanks for your help, @filiprem |
|
Mar 1 |
comment |
“custom archiver out of memory” error when restoring large DB using pg_restore There is nothing wrong with the record with id = 463110542, but all of those numbers after line 463110542: above don't look like my data. Do you know how to interpret that line number? |
|
Mar 1 |
revised |
“custom archiver out of memory” error when restoring large DB using pg_restore timeline details |
|
Mar 1 |
asked | “custom archiver out of memory” error when restoring large DB using pg_restore |
|
Nov 15 |
comment |
How does postgres use the schema search path when making indexes? I'm planning on doing a rails pull request for this once I test your proposed change and make sure this will fix the problem... I'll link to this post and mention your contribution by name, if that's OK. |
|
Nov 15 |
awarded | Scholar |
|
Nov 15 |
accepted | How does postgres use the schema search path when making indexes? |
|
Nov 14 |
awarded | Editor |
|
Nov 14 |
revised |
How does postgres use the schema search path when making indexes? added 1110 characters in body |
|
Nov 14 |
comment |
How does postgres use the schema search path when making indexes? Thanks Craig... I dug a little deeper based on your proof of concept here. Question updated. |
|
Nov 14 |
awarded | Student |
|
Nov 14 |
asked | How does postgres use the schema search path when making indexes? |
