On Mon, 2007-12-10 at 22:43 -0600, Brett Neumeier wrote:
> It seems that the recovery command always copies the source WAL file
> (with a name like 00010002009C) to a file path
> "pg_xlog/RECOVERYXLOG", which is fine. However, then when we abort
> recovery, postgresql seems to expect t
On Mon, 2007-12-10 at 23:18 -0500, Tom Lane wrote:
> Erik Jones <[EMAIL PROTECTED]> writes:
> If you dig in the PG archives you will find some discussions of
> inventing a "real equality" flag for operators, which would authorize
> the planner to make such deductions for any immutable operator/fun
Hello everybody,
I did encounter a behaviour of aliases on my postgresql 8.1, which I don't
quite understand.
Consider this schema layout:
CREATE TABLE t1
(
id serial NOT NULL,
t2_id integer NOT NULL,
t3_id integer NOT NULL,
t1_name character varying(255),
CONSTRAINT t1_pke
I messed up a little while reformatting, the error message is of course:
ERROR: column "got_t2_id" does not exist
_
Von: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] Im Auftrag von Stanislav Raskin
Gesendet: Dienstag, 11. Dezember 2007 12:33
An: pgsql-general@postgresql.org
Betre
Note to self: works if I directly reference outer query column name from the
inner query.
Still no Idea why it does not work with the alias.
On Dec 10, 2007 8:01 PM, Erik Jones <[EMAIL PROTECTED]> wrote:
>
[snip]
> Again, though, is there some better way to go about implementing some
> kind of hash based partitioning in postgres besides this that would
> be more natural wrt queries?
>
Adding a column to hold the result of the %, perha
On Mon, Dec 10, 2007 at 02:00:24PM -0800, Reece Hart wrote:
>
> On Mon, 2007-12-10 at 13:31 -0800, hjenkins wrote:
>
> > I would like to take a timeseries of data and extract the rows of data
> > flanking the gaps in it. So I need to compare timestamps from two
> > adjacent
> > rows, and determin
Hi all
I've recently installed pg 8.2.5 on a new server and transferred my data
from 8.2.4 running on a slow old thing, via pg_dump.
One of these tables has point UK address data, with 27 million rows, and
another the UK roads data, approx 4 million rows.
My problem is I have several text fields
Thanks. Im testing slony1-1.2.12 in postgres 8.3beta3 version. I tried to
configure slony but I keep getting this error.
./configure --with-pgconfigdir=/export/home/sjothirajah/postgres8.3/bin
--with-enable-thread-safety
or
./configure --with-pgconfigdir=/export/home/sjothirajah/postgres8.3/bin
-
Someone scolding wrote:
Please don't hijack other threads, the original thread was 'TIMESTAMP
difference'.
(don't answer to an arbitrary other mail and change the subject. Every
mail contains references-header)
I apologize; I had assumed that the threads were simply grouped by
subj
William Temperley wrote:
My problem is I have several text fields in the address data, for which
postgres ignores the indexes (btree).
"Index Scan using ap_idx_pc on ap (cost= 0.00..15.30 rows=1 width=188)"
" Index Cond: (((pc_)::text >= 'OX2 0'::character varying) AND ((pc_)::text
< 'OX2 1'
Keith Turner wrote:
Someone scolding wrote:
Please don't hijack other threads, the original thread was 'TIMESTAMP
difference'.
I think it was probably intended as a *gentle* scolding. We try to be as
polite as possible on the PG lists. Particularly important given their
international nature
Thank you for your response. What may be obvious to some isn't always to
others. It's never a bad idea to remind users how you want your data
formatted if there are roadblocks that are not obvious on the surface.
Thanks again...
K.
-Original Message-
From: Richard Huxton [mailto:[EMAIL
On Dec 11, 2007, at 7:20 AM, Mike Rylander wrote:
On Dec 10, 2007 8:01 PM, Erik Jones <[EMAIL PROTECTED]> wrote:
[snip]
Again, though, is there some better way to go about implementing some
kind of hash based partitioning in postgres besides this that would
be more natural wrt queries?
A
am Tue, dem 11.12.2007, um 14:57:57 + mailte Richard Huxton folgendes:
> Keith Turner wrote:
> >Someone scolding wrote:
I wrote this ;-)
> >
> >Please don't hijack other threads, the original thread was 'TIMESTAMP
> >difference'.
>
> I think it was probably intended as a *gentle* scolding.
"Stanislav Raskin" <[EMAIL PROTECTED]> writes:
> Still no Idea why it does not work with the alias.
SELECT-list output aliases name the *output* columns of the SELECT.
Those output columns are not available to the SELECT's computation
clauses. Otherwise you'd have a logical circularity --- by def
>
> Well, given that the bin is computed as a function of some_id, the
> most natural way would be to not have to mention that bin in SELECT
> statements at all. However, it does appear that either a.) including
> the bin as a table attribute and in the where clause (either directly
> or the compu
"Erik Jones" <[EMAIL PROTECTED]> writes:
> Well, given that the bin is computed as a function of some_id, the most
> natural way would be to not have to mention that bin in SELECT statements at
> all.
The problem Tom's tried to explain is that the function may or may not
preserve the bin. So
I recently discovered the hashtext() function, and I'm interested in using
it to reduce the size of one of the biggest indexes in my database.
I have a table of URLs with a unique index on the URL. Some of these URLs
are very long (we truncate them at 1024 characters), and we have many
millions of
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Tue, 11 Dec 2007 06:48:35 -0800
"Keith Turner" <[EMAIL PROTECTED]> wrote:
>
> I apologize; I had assumed that the threads were simply grouped by
> subject. If this is such a problem, probably it should be laid out on
> the list information page, o
On 11/12/2007 14:57, Richard Huxton wrote:
It's one of those "common knowledge" things that are obvious to everyone
who's done it once themselves. It's just part of the nature of how email
works. Google around "mailing list etiquette" and you should see plenty
of guidelines.
It might be a go
could i use a sentence similar to the mysql sentence
insert if not exist into SP values ('cesp','sp');
in postgresql?
pau
--
Pau Marc Muñoz Torres
Laboratori de Biologia Computacional
Institut de Biotecnologia i Biomedicina Vicent
Villar
Universitat Autonoma de Barcelona
E-08193 Bellaterr
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Tue, 11 Dec 2007 16:31:40 +
"Raymond O'Donnell" <[EMAIL PROTECTED]> wrote:
> //
> Please note in particular the following points of netiquette:
>
> * Don't top-post, as it makes for confusing reading.
>
> * Don't start a new thread by re
; di NELLY FURTADO
Clicca qui: http://adv.email.it/cgi-bin/foclick.cgi?mid=6617&d=20071211
---(end of broadcast)---
TIP 6: explain analyze is your friend
On Tue, Dec 11, 2007 at 08:43:44AM -0800, Joshua D. Drake wrote:
>
> O.k. this might be a bit snooty but frankly it is almost 2008. If you
> are still a top poster, you obviously don't care about the people's
> content that you are replying to, to have enough wits to not top post.
There are those
Hi List,
I'm trying to write a batch file that executes a query in PostgreSQL.
Depending on the output of the query, the batch file does one of two
things, jumps to a line that has a command to export a table from
PostgreSQL, or calls another batch file, which copies some files.
What provin
On Jul 29, 2007 2:51 PM, Magnus Hagander <[EMAIL PROTECTED]> wrote:
> Mitchell Vincent wrote:
> > Ah, I see what you mean.
> >
> > I was hoping to be able to rebuild the MSI to not include the things I
> > didn't need but that doesn't look like it's going to be the case
> > Humbug.. Is there an
Andrew Sullivan wrote:
On Tue, Dec 11, 2007 at 08:43:44AM -0800, Joshua D. Drake wrote:
O.k. this might be a bit snooty but frankly it is almost 2008. If you
are still a top poster, you obviously don't care about the people's
content that you are replying to, to have enough wits to not top po
Hello
On 11/12/2007, Pau Marc Munoz Torres <[EMAIL PROTECTED]> wrote:
> could i use a sentence similar to the mysql sentence
>
> insert if not exist into SP values ('cesp','sp');
>
insert into sp
select 'cesp','sp'
except
select * from SP;
Regards
Pavel Stehule
> in postgresql?
>
> pau
>
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Tue, 11 Dec 2007 17:50:14 +0100
"Matt Doughty" <[EMAIL PROTECTED]> wrote:
> Hi List,
>
>
>
> I'm trying to write a batch file that executes a query in PostgreSQL.
> Depending on the output of the query, the batch file does one of two
> things,
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Tue, 11 Dec 2007 11:49:54 -0500
Andrew Sullivan <[EMAIL PROTECTED]> wrote:
> On a mailing list, perhaps one can argue that the conventions simply
> have to be followed. But I know I find it pretty annoying to get 36
> lines of quoted text followed
-Original Message-
From: [EMAIL PROTECTED] on behalf of Joshua D. Drake
Sent: Tue 12/11/2007 9:43 AM
To: [EMAIL PROTECTED]
Cc: pgsql-general@postgresql.org
Subject: Re: [GENERAL] Hijack!
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Tue, 11 Dec 2007 16:31:40 +
"Raymond O'Donnell
On Dec 11, 2007 10:49 AM, Andrew Sullivan <[EMAIL PROTECTED]> wrote:
> On Tue, Dec 11, 2007 at 08:43:44AM -0800, Joshua D. Drake wrote:
> >
> > O.k. this might be a bit snooty but frankly it is almost 2008. If you
> > are still a top poster, you obviously don't care about the people's
> > content t
"Andrew Sullivan" <[EMAIL PROTECTED]> writes:
> On a mailing list, perhaps one can argue that the conventions simply have to
> be followed. But I know I find it pretty annoying to get 36 lines of quoted
> text followed by something like, "No: see the manual, section x.y.z."
That's because the re
Genius!
Thanks Richard,
The old locale was C and the new one English_United Kingdom.1252
I created a new index with "varchar_pattern_ops" and off it went!
> the strange thing is my btree indexes on the uk roads data work fine.
>
> Do they use like, or explicit range-checks?
>
> I wasn't using l
On Dec 11, 2007, at 9:44 AM, Gregory Stark wrote:
"Erik Jones" <[EMAIL PROTECTED]> writes:
Well, given that the bin is computed as a function of some_id,
the most
natural way would be to not have to mention that bin in SELECT
statements at
all.
The problem Tom's tried to explain is th
Joshua D. Drake wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Tue, 11 Dec 2007 11:54:12 -0500
Thomas Hart <[EMAIL PROTECTED]> wrote:
I agree. Obviously there is convention, and I will post in the style
generally accepted in the list, but to me it always made more sense
to top po
On Dec 11, 2007, at 8:43 AM, Joshua D. Drake wrote:
On Tue, 11 Dec 2007 16:31:40 +
"Raymond O'Donnell" <[EMAIL PROTECTED]> wrote:
//
Please note in particular the following points of netiquette:
* Don't top-post, as it makes for confusing reading.
* Don't start a new thread by repl
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Tue, 11 Dec 2007 11:54:12 -0500
Thomas Hart <[EMAIL PROTECTED]> wrote:
> I agree. Obviously there is convention, and I will post in the style
> generally accepted in the list, but to me it always made more sense
> to top post. If you're keeping u
--- On Tue, 12/11/07, Pau Marc Munoz Torres <[EMAIL PROTECTED]> wrote:
> could i use a sentence similar to the mysql sentence
>
> insert if not exist into SP values
> ('cesp','sp');
>
> in postgresql?
Using standard ANSI-SQL the statement could be re-written:
INSERT INTO SP
SELECT a, b
Andrew Sullivan <[EMAIL PROTECTED]> writes:
> On a mailing list, perhaps one can argue that the conventions simply have to
> be followed. But I know I find it pretty annoying to get 36 lines of quoted
> text followed by something like, "No: see the manual, section x.y.z."
Indeed, and that's why a
On Dec 11, 2007, at 10:08 AM, Erik Jones wrote:
b.) precomputing the bin and directly accessing the child table will
be the only options we have for now.
This is where I'm headed I have only one or two queries that don't
specify the partitioned ID, and those need a full table scan anyh
William Temperley wrote:
Genius!
Thanks Richard,
The old locale was C and the new one English_United Kingdom.1252
I created a new index with "varchar_pattern_ops" and off it went!
Catches everyone first time.
--
Richard Huxton
Archonet Ltd
---(end of broadcast)--
On Dec 11, 2007, at 10:44 AM, Gregory Stark wrote:
The problem Tom's tried to explain is that the function may or may not
preserve the bin. So for example if you wanted to bin based on the
final digit
of a numeric number, so you had a constraint like
I, along with at least Erik, was thinki
On Tue, Dec 11, 2007 at 09:00:05AM -0800, Joshua D. Drake wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> On Tue, 11 Dec 2007 11:49:54 -0500
> Andrew Sullivan <[EMAIL PROTECTED]> wrote:
>
> > On a mailing list, perhaps one can argue that the conventions simply
> > have to be followed
[EMAIL PROTECTED] wrote:
Hi list.
Does someone know if there is some kind of incompatibility between POSIX
(glibc 2.4) and libpq (postgres 8.2) on Linux RedHat 5.0?
Do you really mean RedHat 5.0 - the one released in 1997?
--
Richard Huxton
Archonet Ltd
---(end o
Gregory Williamson wrote:
* Try to see the world from a perspective other that your own
(admittedly superior) one ! Not everyone is so advanced.
* Get a life -- how people post is _trivial_. *content* over *form* !
Beating dead horses is of no interest other than the inherent joy in
the thing.
Mitchell Vincent wrote:
> On Jul 29, 2007 2:51 PM, Magnus Hagander <[EMAIL PROTECTED]> wrote:
>> Mitchell Vincent wrote:
>>> Ah, I see what you mean.
>>>
>>> I was hoping to be able to rebuild the MSI to not include the things I
>>> didn't need but that doesn't look like it's going to be the case..
"Gregory Williamson" <[EMAIL PROTECTED]> writes:
> Confidentiality Notice: This e-mail message, including any attachments, is for
> the sole use of the intended recipient(s) and may contain confidential and
> privileged information and must be protected in accordance with those
> provisions. Any
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Tue, 11 Dec 2007 10:03:39 -0700
"Gregory Williamson" <[EMAIL PROTECTED]> wrote:
> >
> > However, I would also note that in "windows" world, it is very
> > common to top post. I am constantly retraining very smart, just
> > very ignorant customers.
Steve Atkins <[EMAIL PROTECTED]> writes:
> In the business world it's common to top-post and not cut previous
> content
> - and often appropriate, as it tends to be a communication between a
> smaller number of people, and the uncut content provides context for
> future reference.
> Those who ra
In response to "Gregory Williamson" <[EMAIL PROTECTED]>:
>
> -Original Message-
> From: [EMAIL PROTECTED] on behalf of Joshua D. Drake
> Sent: Tue 12/11/2007 9:43 AM
> To: [EMAIL PROTECTED]
> Cc: pgsql-general@postgresql.org
> Subject: Re: [GENERAL] Hijack!
>
> -BEGIN PGP SIGNED MESS
On Tuesday 11. December 2007, Andrew Sullivan wrote:
>I don't think top posting is always the crime it's made to be (and I
> get a little tired of lectures to others about it on these lists).
It certainly isn't a crime. But it's a bit like thread hijacking in the
sense that a well-formed inline
Vivek Khera <[EMAIL PROTECTED]> writes:
> I, along with at least Erik, was thinking that the constraint
> expression would be evaluated to determine whether to include the
> partition in the final plan. Based on Tom's description, it is not
> the case: the planner basically proves that the c
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Tue, 11 Dec 2007 17:37:27 +
Gregory Stark <[EMAIL PROTECTED]> wrote:
>
> "Gregory Williamson" <[EMAIL PROTECTED]> writes:
>
> > Confidentiality Notice: This e-mail message, including any
> > attachments, is for the sole use of the intended re
On Dec 11, 2007, at 9:40 AM, Tom Lane wrote:
Steve Atkins <[EMAIL PROTECTED]> writes:
In the business world it's common to top-post and not cut previous
content
- and often appropriate, as it tends to be a communication between a
smaller number of people, and the uncut content provides context
> People frequently think that because ORDER BY can refer to the
> output-column aliases, other clauses should be able to do it too,
> but this is not so.
Thank you very much for clearing that one up.
Now I have a follow-up question. Let's assume that I want not only to
evaluate a subquery for th
On Dec 11, 2007 11:41 AM, Leif B. Kristensen <[EMAIL PROTECTED]> wrote:
>
> It certainly isn't a crime. But it's a bit like thread hijacking in the
> sense that a well-formed inline posting is more likely to attract
> intelligent replies. I don't think that I'm the only one who tends to
> skip top
"Matt Magoffin" <[EMAIL PROTECTED]> writes:
> Hello, I'm trying to write a query to return an XML document like
>
>
>
> ...
>
Something like this:
regression=# select xmlelement(name root, xmlagg(x)) from
regression-# (select xmlelement(name range, xmlattributes(string4, count(*)
as
Stanislav,
SELECT
>t2.id,
>(SELECT COUNT(id) FROM t4 WHERE t2_id = t2.id AND value=10)
> AS t4_num
> FROM
>t2
> WHERE
>t2.active
>AND (
> (SELECT COUNT(id) FROM t4 WHERE t2_id = t2.id AND value=10) <= 3
>)
>
>
On Dec 11, 2007, at 12:00 PM, Scott Marlowe wrote:
On Dec 11, 2007 11:41 AM, Leif B. Kristensen <[EMAIL PROTECTED]>
wrote:
It certainly isn't a crime. But it's a bit like thread hijacking
in the
sense that a well-formed inline posting is more likely to attract
intelligent replies. I don't
> should do the trick without double select, or?
Indeed it seems to do so. The cost estimation is even about 10 times less
with the real application's queries.
I never really used group/having even though being aware of their existence.
I probably should do so more often.
Hi,
Is it possible to implement postgres version upgrade using WAL files?
Currently the WAL file replication donot work between two different postgres
version. Is there a posiibility to implement this using WAL files so that when
I want to upgrade to the latest version I can use these WAL?
Thank
SHARMILA JOTHIRAJAH wrote:
Hi,
Is it possible to implement postgres version upgrade using WAL files?
Currently the WAL file replication donot work between two different
postgres version. Is there a posiibility to implement this using WAL
files so that when I want to upgrade to the latest versio
On 12/10/07, Keith Turner <[EMAIL PROTECTED]> wrote:
> We are running 8.1 on Windows 2003 server and have had a server crash
> over the weekend. A virus is suspected - we maintain an app server on
> someone else's network, though we do have anti-virus running, the
> symptoms were worrying - so we
You are quite right, and I must admit that I messed up one more time on this
one.
I chose an alias, which was already a column name in one of the relations,
so the results were rubbish anyhow.
Took me some time to figure that out.
_
Von: Vyacheslav Kalinin [mailto:[EMAIL PROTECTED]
Scott Marlowe wrote:
On Dec 11, 2007 11:41 AM, Leif B. Kristensen <[EMAIL PROTECTED]> wrote:
It certainly isn't a crime. But it's a bit like thread hijacking in the
sense that a well-formed inline posting is more likely to attract
intelligent replies. I don't think that I'm the only one who t
Collin Kidder wrote:
Scott Marlowe wrote:
On Dec 11, 2007 11:41 AM, Leif B. Kristensen <[EMAIL PROTECTED]> wrote:
I have to suffer through dealing with people like the two of you quoted
above. You can deal with people who'd like to top post. Anything else is
just being a spoiled baby who can
joining column's datatypes do not
>match
>
>
>
--
Email.it, the professional e-mail, gratis per te: http://www.email.it/f
Sponsor:
Fai squillare la PANTERA ROSA sul tuo cellulare: e' in REGALO
Clicca qui: http://adv.email.it/cgi-bin/foclick.cgi?mid=6613&
Thomas Hart wrote:
I agree. Obviously there is convention, and I will post in the
style generally accepted in the list, but to me it always made more
sense to top post. If you're keeping up on the conversation, then
the relevant information is right there, and if you weren't, it's
not tha
[EMAIL PROTECTED] wrote:
Does someone know if there is some kind of incompatibility between
POSIX
(glibc 2.4) and libpq (postgres 8.2) on Linux RedHat 5.0?
Do you really mean RedHat 5.0 - the one released in 1997?
> Sorry, my information was not complete.
> The Linux version is Linux AS 5.0
It seems that in create table I cannot specify the schema of a built-in
type that has a length specifier. Nor can I double-quote the type name.
Is this correct/expected behaviour, and are there work-arounds?
This works fine:
create table "public"."additional" (
"str1""pg_catalo
John D. Burger wrote:
Thomas Hart wrote:
I agree. Obviously there is convention, and I will post in the style
generally accepted in the list, but to me it always made more sense
to top post. If you're keeping up on the conversation, then the
relevant information is right there, and if you wer
"Andrew Sullivan" <[EMAIL PROTECTED]> writes:
> I would argue that this message is harder to read than if I'd just replied
> at the top. It's pointlessly long -- but without including everything, you
> wouldn't have all the context, and you might have missed something.
We're not goldfish, we
On Tue, Dec 11, 2007 at 07:44:31PM +, Gregory Stark wrote:
> Seriously, do you have any trouble following the discussion even though I
> only clipped two sentences of your message? If you did would you have any
> trouble finding the original message to reread it?
No, but (1) I have been doing
On Tuesday 11 December 2007 12:23, Andrew Sullivan wrote:
> Simply replying to an argument with an assertion to the contrary is, I
> think, dogmatism. The argument for top posting is that it is _easier_ to
> read for certain kinds of cases. I have already rehearsed those arguments;
> I think they
On Tuesday 11 December 2007 12:23, Andrew Sullivan wrote:
> On Tue, Dec 11, 2007 at 09:00:05AM -0800, Joshua D. Drake wrote:
> > -BEGIN PGP SIGNED MESSAGE-
> > Hash: SHA1
> >
> > On Tue, 11 Dec 2007 11:49:54 -0500
> >
> > Andrew Sullivan <[EMAIL PROTECTED]> wrote:
> > > On a mailing list, p
Thomas Hart wrote:
As an illustration, which helps you understand the preceding
paragraph better, the extract above, or the mess below?
You raise some good points, and I agree with them. However if you
want to have an intelligent conversation, try not to load it with
questions like "Do yo
Richard Huxton <[EMAIL PROTECTED]> writes:
>>> [EMAIL PROTECTED] wrote:
Does someone know if there is some kind of incompatibility between
POSIX (glibc 2.4) and libpq (postgres 8.2) on Linux RedHat 5.0?
>>> Do you really mean RedHat 5.0 - the one released in 1997?
>> Sorry, my informat
ex:
CREATE TRIGGER mytrig AFTER INSERT OR UPDATE ON foo1 FOR EACH ROW EXECUTE
PROCEDURE updatefoo1('datarow');
The command itself is able to be executed without error. However, what then
happens, is that whenever the application attempts to insert a record into
foo1, it simply doesn't insert. On
Steve Atkins wrote:
In the business world it's common to top-post and not cut previous content
- and often appropriate, as it tends to be a communication between a
smaller number of people, and the uncut content provides context for
future reference.
And it is quite common for tractor trailers
On Dec 11, 2007 3:35 PM, smiley2211 <[EMAIL PROTECTED]> wrote:
> Thanks...Michelle
Please post DDL plus sample code/data to increase the odds of having
someone help you.
---(end of broadcast)---
TIP 4: Have you searched our list archives?
Collin Kidder wrote:
I have to suffer through dealing with people like the two of you quoted
above. You can deal with people who'd like to top post. Anything else is
just being a spoiled baby who can't deal with minor issues. If all the
energy spent crying about top posting were used to fuel c
Joshua D. Drake wrote:
Geoffrey wrote:
Collin Kidder wrote:
I have to suffer through dealing with people like the two of you
quoted above. You can deal with people who'd like to top post.
Anything else is just being a spoiled baby who can't deal with minor
issues. If all the energy spent cry
Geoffrey wrote:
Collin Kidder wrote:
I have to suffer through dealing with people like the two of you
quoted above. You can deal with people who'd like to top post.
Anything else is just being a spoiled baby who can't deal with minor
issues. If all the energy spent crying about top posting we
Geoffrey wrote:
Collin Kidder wrote:
I have to suffer through dealing with people like the two of you
quoted above. You can deal with people who'd like to top post.
Anything else is just being a spoiled baby who can't deal with minor
issues. If all the energy spent crying about top posting we
I felt I was 'responding in kind' wrt 'it really irritates me when
people cry like 4 year olds about top posting. It's not that bad, get
over it.' posting. My apologies if I've taken it to a level of rude
that it had not already reached.
I suppose that the post was probably directed at
Collin Kidder wrote:
Geoffrey wrote:
Collin Kidder wrote:
I have to suffer through dealing with people like the two of you
quoted above. You can deal with people who'd like to top post.
Anything else is just being a spoiled baby who can't deal with minor
issues. If all the energy spent cryin
If I create a binary cursor on a recent version of PostgreSQL, how can I
tell if the timestamp data internally is an 8 byte double or an 8 byte
integer?
I see an #ifdef that changes the code path to compute timestamps as one
type or the other, but I do not know how to recognize the internal
format
On Dec 11, 2007 2:58 PM, Collin Kidder <[EMAIL PROTECTED]> wrote:
> Geoffrey wrote:
> > Collin Kidder wrote:
> >
> >> I have to suffer through dealing with people like the two of you
> >> quoted above. You can deal with people who'd like to top post.
> >> Anything else is just being a spoiled baby
On Dec 11, 2007 1:01 PM, Collin Kidder <[EMAIL PROTECTED]> wrote:
> Scott Marlowe wrote:
> > On Dec 11, 2007 11:41 AM, Leif B. Kristensen <[EMAIL PROTECTED]> wrote:
> >
> >> It certainly isn't a crime. But it's a bit like thread hijacking in the
> >> sense that a well-formed inline posting is more
"Dann Corbit" <[EMAIL PROTECTED]> writes:
> If I create a binary cursor on a recent version of PostgreSQL, how can I
> tell if the timestamp data internally is an 8 byte double or an 8 byte
> integer?
PQparameterStatus(conn, "integer_datetimes")
regards, tom lane
Dann Corbit wrote:
> If I create a binary cursor on a recent version of PostgreSQL, how can I
> tell if the timestamp data internally is an 8 byte double or an 8 byte
> integer?
>
> I see an #ifdef that changes the code path to compute timestamps as one
> type or the other, but I do not know how t
I agree with Joshua on this point. It's entirely possible to discuss
this without resorting to immaturity. If you make a decent point, then
diminish it by cursing or insulting everybody here, you've lost the
point and it's effectiveness entirely.
Yes, once again, I apologize. At times I se
On Tue, 11 Dec 2007 12:00:00 -0600
"Scott Marlowe" <[EMAIL PROTECTED]> wrote:
> You're certainly not. I can't tell you how many times I've
> carefully replied to someone with inline quoting, only to get some
> top post response. I then ask them politely not to top post, fix
> the format, reply,
> -Original Message-
> From: Alvaro Herrera [mailto:[EMAIL PROTECTED]
> Sent: Tuesday, December 11, 2007 1:11 PM
> To: Dann Corbit
> Cc: [EMAIL PROTECTED]; pgsql-general@postgresql.org
> Subject: Re: [GENERAL] Dumb question about binary cursors and
> #ifdefHAVE_INT64_TIMESTAMP
>
> Dann Cor
On Dec 11, 2007, at 2:58 PM, Collin Kidder wrote:
Geoffrey wrote:
Collin Kidder wrote:
I have to suffer through dealing with people like the two of you
quoted above. You can deal with people who'd like to top post.
Anything else is just being a spoiled baby who can't deal with
minor iss
In response to Collin Kidder <[EMAIL PROTECTED]>:
> Geoffrey wrote:
> > Collin Kidder wrote:
> >
> >> I have to suffer through dealing with people like the two of you
> >> quoted above. You can deal with people who'd like to top post.
> >> Anything else is just being a spoiled baby who can't dea
On Dec 11, 2007, at 1:44 PM, Gregory Stark wrote:
"Andrew Sullivan" <[EMAIL PROTECTED]> writes:
I would argue that this message is harder to read than if I'd just
replied
at the top. It's pointlessly long -- but without including
everything, you
wouldn't have all the context, and you mi
> -Original Message-
> From: Alvaro Herrera [mailto:[EMAIL PROTECTED]
> Sent: Tuesday, December 11, 2007 1:11 PM
> To: Dann Corbit
> Cc: [EMAIL PROTECTED]; pgsql-general@postgresql.org
> Subject: Re: [GENERAL] Dumb question about binary cursors and
> #ifdefHAVE_INT64_TIMESTAMP
>
> Dann Cor
1 - 100 of 146 matches
Mail list logo
