From: Bud Rogers <budr@sirinet.net>
Subject: thread ordering, root last
Date: 24 Jul 2000 04:56:26 -0500 [thread overview]
Message-ID: <87lmyrg8c5.fsf@twocups.sirinet.net> (raw)
I just subscribed to the pgsql-hackers list. Haven't yet made any changes
to group parameters, etc. In the summary buffer the messages are arranged
in threads but in every case the root of the thread is listed last. I have
seen this occasionally with other groups, but never quite so consistently.
Is this a problem with gnus, with the list, or with my setup?
R +[ 43: Adriaan Jouber] Re: [HACKERS] Loading binary data into the database
+[ 33: Tom Lane ] Re: [HACKERS] Loading binary data into the database
+[ 36: Adriaan Jouber] Re: [HACKERS] Loading binary data into the database
+[ 15: Tom Lane ] Re: [HACKERS] Loading binary data into the database
+[ 36: Adriaan Jouber] [HACKERS] Loading binary data into the database
+[ 15: Hannu Krosing ] Re: [HACKERS] 8Ko limitation
+[ 7: Tom Lane ] Re: [HACKERS] 8Ko limitation
+[ 34: "Justin Hickey] Re: [HACKERS] 8Ko limitation
+[ 14: Karel Zak ] Re: [HACKERS] 8Ko limitation
+[ 20: "Xavier ZIMMER] [HACKERS] 8Ko limitation
+[ 46: Tom Lane ] Re: [HACKERS] About these IPC parameters
+[ 12: "Henry B. Hotz] Re: [HACKERS] About these IPC parameters
+[ 24: The Hermit Hac] Re: [HACKERS] About these IPC parameters
+[ 29: Peter Eisentra] Re: [HACKERS] About these IPC parameters
+[ 16: Peter Eisentra] Re: [HACKERS] About these IPC parameters
+[ 44: Tom Lane ] Re: [HACKERS] About these IPC parameters
+[ 36: Peter Eisentra] [HACKERS] About these IPC parameters
+[ 23: Jan Wieck ] Re: [HACKERS] About TOAST and indices
+[ 8: Tom Lane ] Re: [HACKERS] About TOAST and indices
+[ 33: Jan Wieck ] [HACKERS] About TOAST and indices
+[ 12: "Mikheev, Vadi] RE: [HACKERS] btree split logic is fragile in the presence of lar
+[ 16: "Mikheev, Vadi] RE: [HACKERS] btree split logic is fragile in the presence of lar
+[ 14: "Mikheev, Vadi] RE: [HACKERS] btree split logic is fragile in the presence of lar
+[ 19: "Mikheev, Vadi] RE: [HACKERS] btree split logic is fragile in the presence of lar
+[ 33: Tom Lane ] Re: [HACKERS] btree split logic is fragile in the presence of lar ge index items
+[ 22: "Hiroshi Inoue] RE: [HACKERS] btree split logic is fragile in the presence of lar ge index items
+[ 37: Tom Lane ] Re: [HACKERS] btree split logic is fragile in the presence of lar ge index items
+[ 21: "Hiroshi Inoue] RE: [HACKERS] btree split logic is fragile in the presence of lar ge index items
+[ 28: Tom Lane ] Re: [HACKERS] btree split logic is fragile in the presence of lar ge index items
+[ 16: Tom Lane ] Re: [HACKERS] btree split logic is fragile in the presence of large index items
+[ 9: Thomas Lockhar] Re: [HACKERS] Geometry test broken
+[ 23: Jan Wieck ] [HACKERS] Geometry test broken
R +[ 19: The Hermit Hac] Re: [HACKERS] Hello PL/Python
R +[ 14: Tom Lane ] Re: [HACKERS] Hello PL/Python
R +[ 22: Hannu Krosing ] Re: [HACKERS] Hello PL/Python
R +[ 30: Jan Wieck ] Re: [HACKERS] Hello PL/Python
R +[ 14: Tom Lane ] Re: [HACKERS] Hello PL/Python
R +[ 11: Karel Zak ] Re: [HACKERS] Hello PL/Python
R +[ 31: Hannu Krosing ] Re: [HACKERS] Hello PL/Python
R +[ 21: "Henry B. Hotz] Re: [HACKERS] How PostgreSQL's floating-point hurts everyone
R +[ 7: Thomas Lockhar] Re: [HACKERS] How PostgreSQL's floating-point hurts everyone everywhere
R +[ 11: Tom Lane ] Re: [HACKERS] How PostgreSQL's floating-point hurts everyone everywhere
R +[ 68: Jan Wieck ] Re: [HACKERS] How PostgreSQL's floating-point hurts everyone everywhere
R +[ 51: Thomas Lockhar] Re: [HACKERS] How PostgreSQL's floating-point hurts everyone everywhere
R +[ 48: Peter Eisentra] [HACKERS] How PostgreSQL's floating-point hurts everyone everywhere
+[ 14: Larry Rosenman] [HACKERS] INET/CIDR types
+[ 28: Larry Rosenman] Re: [HACKERS] mac.c
+[ 14: Thomas Lockhar] Re: [HACKERS] mac.c
+[ 18: Larry Rosenman] [HACKERS] mac.c
+[ 7: Larry Rosenman] [HACKERS] mac.c
+[ 35: Larry Rosenman] Re: [HACKERS] my stupidity
+[ 25: John McKown ] Re: [HACKERS] my stupidity
+[ 12: Larry Rosenman] [HACKERS] my stupidity
+[ 30: Philip Warner ] [HACKERS] pg_dump with BLOBs UPDATED
+[ 53: Peter Eisentra] Re: [HACKERS] pg_dump, libdump, dump API, & backend again
+[ 73: Philip Warner ] [HACKERS] pg_dump, libdump, dump API, & backend again
+[ 21: Jan Wieck ] [HACKERS] PGLZ memory problems fixed
+[ 27: Chris Bitmead ] Re: [HACKERS] Re: [GENERAL] PRIMARY KEY & INHERITANCE (fwd)
+[ 18: Tom Lane ] Re: [HACKERS] Re: [GENERAL] PRIMARY KEY & INHERITANCE (fwd)
+[ 30: "Stephan Szabo] Re: [HACKERS] Re: [GENERAL] PRIMARY KEY & INHERITANCE (fwd)
+[ 31: Chris Bitmead ] Re: [HACKERS] Re: [GENERAL] PRIMARY KEY & INHERITANCE (fwd)
+[ 25: "Stephan Szabo] Re: [HACKERS] Re: [GENERAL] PRIMARY KEY & INHERITANCE (fwd)
+[ 27: Chris Bitmead ] Re: [HACKERS] Re: [GENERAL] PRIMARY KEY & INHERITANCE (fwd)
+[ 15: Peter Eisentra] [HACKERS] Re: [PATCHES] locale changes
+[ 75: Tom Lane ] [HACKERS] Re: lost records --- problem identified!
+[ 32: "Oliver Elphic] Re: [HACKERS] Shared library search paths
+[ 41: Peter Eisentra] Re: [HACKERS] Shared library search paths
+[ 10: Thomas Lockhar] Re: [HACKERS] State of RPMs
+[ 23: Trond Eivind G] Re: [HACKERS] State of RPMs
+[ 11: Thomas Lockhar] Re: [HACKERS] State of RPMs
+[ 12: Trond Eivind G] Re: [HACKERS] State of RPMs
+[ 9: Thomas Lockhar] [HACKERS] State of RPMs
+[ 14: Larry Rosenman] [HACKERS] Stupid Me...
+[ 42: Jan Wieck ] Re: [HACKERS] TOAST & vacuum
+[ 25: Tom Lane ] Re: [HACKERS] TOAST & vacuum
+[ 23: Jan Wieck ] [HACKERS] TOAST & vacuum
+[ 35: Philip Warner ] Re: [HACKERS] TODO updates
+[ 19: Tom Lane ] Re: [HACKERS] TODO updates
+[ 38: Philip Warner ] Re: [HACKERS] TODO updates
+[ 20: Tom Lane ] Re: [HACKERS] TODO updates
+[ 26: Philip Warner ] Re: [HACKERS] TODO updates
+[ 65: Tom Lane ] Re: [HACKERS] TODO updates
+[ 10: Tom Lane ] Re: [HACKERS] TODO updates
+[ 25: Philip Warner ] Re: [HACKERS] TODO updates
+[ 57: Peter Eisentra] [HACKERS] TODO updates
+[ 40: Mikhail Terekh] Re: [HACKERS] Untrusted PL/Tcl?
+[ 33: Larry Rosenman] Re: [HACKERS] Update: mac.c update, patch now on ftp
+[ 18: Thomas Lockhar] Re: [HACKERS] Update: mac.c update, patch now on ftp
+[ 36: Tom Lane ] Re: [HACKERS] Vaccuum allows read access?
+[ 33: Jan Wieck ] Re: [HACKERS] Vaccuum allows read access?
+[ 10: Tom Lane ] Re: [HACKERS] Vaccuum allows read access?
+[ 13: The Hermit Hac] Re: [HACKERS] Vaccuum allows read access?
+[ 14: Bruce Momjian ] Re: [HACKERS] Vaccuum allows read access?
+[ 10: Alfred Perlste] [HACKERS] Vaccuum allows read access?
[ 29: jtnix@my-deja.] ERROR: Relation 'pg_user' does not exist
[ 21: Zardoz ] Importing bool data
--
Bud Rogers <budr@sirinet.net> http://www.sirinet.net/~budr/zamm.html
next reply other threads:[~2000-07-24 9:56 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-07-24 9:56 Bud Rogers [this message]
2000-07-24 12:38 ` Andreas Fuchs
[not found] ` <vafr98cdg5u.fsf@lucy.cs.uni-dortmund.de>
[not found] ` <87hf9897at.fsf@dahaIM.dyndns.org>
[not found] ` <vaf8zuk94c1.fsf@lucy.cs.uni-dortmund.de>
2000-07-30 20:54 ` Bud Rogers
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87lmyrg8c5.fsf@twocups.sirinet.net \
--to=budr@sirinet.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).