From: | Bruce Momjian <maillist(at)candle(dot)pha(dot)pa(dot)us> |
---|---|
To: | tgl(at)sss(dot)pgh(dot)pa(dot)us (Tom Lane) |
Cc: | hackers(at)postgreSQL(dot)org |
Subject: | Re: [HACKERS] Sequence objects have no global currval operator? |
Date: | 1998-07-13 21:50:01 |
Message-ID: | 199807132151.RAA02174@candle.pha.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
How about SELECT * FROM sequence_table_name? Sequence numbers are
stored in their own tables.
> I'm planning to use a "sequence" object to allow multiple clients of a
> shared database to label table records with guaranteed-increasing serial
> numbers. (The underlying problem is to let all the clients efficiently
> find changes that any one of them makes. Every insertion or update will
> assign a new sequence number to each new or modified record; then the
> writer must issue a NOTIFY. Upon being notified, each client can read
> all the newly-modified records with
> SELECT ... FROM table WHERE seqno > lastseqno;
> lastseqno := max(seqno seen in retrieved records);
--
Bruce Momjian | 830 Blythe Avenue
maillist(at)candle(dot)pha(dot)pa(dot)us | Drexel Hill, Pennsylvania 19026
+ If your life is a hard drive, | (610) 353-9879(w)
+ Christ can be your backup. | (610) 853-3000(h)
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 1998-07-13 22:02:51 | Re: [HACKERS] Sequence objects have no global currval operator? |
Previous Message | Bruce Momjian | 1998-07-13 21:31:34 | Re: [HACKERS] Anyone working on optimizing subset min/max queries? |