Search Results
| Search type | Search syntax |
|---|---|
| Tags | [tag] |
| Exact | "words here" |
| Author |
user:1234 user:me (yours) |
| Score |
score:3 (3+) score:0 (none) |
| Answers |
answers:3 (3+) answers:0 (none) isaccepted:yes hasaccepted:no inquestion:1234 |
| Views | views:250 |
| Code | code:"if (foo != bar)" |
| Sections |
title:apples body:"apples oranges" |
| URL | url:"*.example.com" |
| Saves | in:saves |
| Status |
closed:yes duplicate:no migrated:no wiki:no |
| Types |
is:question is:answer |
| Exclude |
-[tag] -apples |
| For more details on advanced search visit our help page | |
Results tagged with sequence
Search options not deleted
user 112341
An object that can generate unique integers.
4
votes
3
answers
852
views
Achieving "sequence number", rather than dateTime, for updates; postgres specifically
So a postgres database (specifically, an AmazonRDS instance fwiw).
It's easy enough to arrange things to get the last updated (or created) time for any record.
That information would be a datetime.
…
- 103
0
votes
1
answer
324
views
A (simple?) solution to the "logical decoding / sequence" problem in Postgres?
After reading this mind-blowing answer by Craig Ringer to my previous question Achieving "sequence number", rather than dateTime, for updates; postgres specifically I've become interested in the "logical … decoding / sequence" racetrack problem in Postgres. …
- 103