a terrible idea. (Frankly, they're a
terrible idea outside that context also, but that ship sailed some
time ago.)
A
--
Andrew Sullivan
[EMAIL PROTECTED]
+1 503 667 4564 x104
http://www.commandprompt.com/
--
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To make
ng the question. I
think you have your answer, even if you don't like it.
A
--
Andrew Sullivan
[EMAIL PROTECTED]
+1 503 667 4564 x104
http://www.commandprompt.com/
--
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mai
On Sun, Nov 23, 2008 at 05:36:13PM +0100, toruvinn wrote:
> Actually, I prefer it the old way. I just like to know the column order
> `SELECT *' would return (though I never use `SELECT *' myself). Not to
You can't know that, as a matter of SQL semantics.
A
--
A
On Mon, Nov 24, 2008 at 01:39:48AM -0500, Andrew Sullivan wrote:
>
> You can't know that, as a matter of SQL semantics.
I shouldn't reply to listmail when bone tired. I was thinking of
rows. Sorry.
A
--
Andrew Sullivan
[EMAIL PROTECTED]
--
Sent via pgsql-bugs mailing
ther this is a bug for postgres seems to depend on whether that
reading is coming from the OS or postgres itself. (I don't know the
answer to that.)
A
--
Andrew Sullivan | [EMAIL PROTECTED]
In the future this spectacle of the middle classes shocking the avant-
garde will p
to be pretty clear that the scope
info is a necessary part of the addressing, so I don't think it can
be thrown away before looking at the address.
A
--
Andrew Sullivan | [EMAIL PROTECTED]
I remember when computers were frustrating because they *did* exactly what
you told them to.
a configuration to the Internet. All my
experience tells me that such things eventually always leak, and I'd
hate for Postgres to be the source of that sort of damage.
A
--
Andrew Sullivan | [EMAIL PROTECTED]
The whole tendency of modern prose is away from concrete
eem that it's rejecting perfectly well-formed
input, which is surely bad.)
A
--
Andrew Sullivan | [EMAIL PROTECTED]
Everything that happens in the world happens at some place.
--Jane Jacobs
---(end of broadcast)---
TIP 7: You
> http://www.postgresql.org/about/donate
--
Andrew Sullivan | [EMAIL PROTECTED]
"The year's penultimate month" is not in truth a good way of saying
November.
--H.W. Fowler
---(end of broadcast)-
e bugs list. Use pgsql-novice instead, I think.
A
--
Andrew Sullivan | [EMAIL PROTECTED]
Everything that happens in the world happens at some place.
--Jane Jacobs
---(end of broadcast)---
TIP 5: don't forget to increase your free space map settings
80 occur
> System Hang.
Uh, do you have proof that your "hanging" system (and what do you
mean by hang, anyway?) doesn't have any hardware or OS problems?
PostgreSQL doesn't know anything more about the hardware than the OS
tells it. If the OS works, PostgreSQL should too
7;d suspect your script. It's nothing like any
actual PostgreSQL bug I've ever heard of. Also, I note that one of
your systems is Pg 7.1. Upgrade that _right now_. Don't use it.
A
--
Andrew Sullivan | [EMAIL PROTECTED]
This work was visionary and imaginative, and goes to
en bitten by too many Linux corner cases not to worry
about the kernel.)
A
--
Andrew Sullivan | [EMAIL PROTECTED]
"The year's penultimate month" is not in truth a good way of saying
November.
--H.W. Fowler
---(end of broadcast)--
On Fri, Aug 24, 2007 at 10:06:56AM -0400, Feng Chen wrote:
> VERSION = PostgreSQL 8.1.2
You know that the project doesn't put out maintenance releases for
the fun of it, right? The latest is 8.1.9 in that series. You need
to upgrade.
A
--
Andrew Sullivan | [EMAIL PROTECTED]
Unfor
On Fri, Aug 24, 2007 at 10:11:06AM -0400, Andrew Sullivan wrote:
> On Fri, Aug 24, 2007 at 10:06:56AM -0400, Feng Chen wrote:
> > VERSION = PostgreSQL 8.1.2
>
> You know that the project doesn't put out maintenance releases for
> the fun of it, right? The latest is 8.1
there doesn't correspond to the linked
text: the question asks about the upgrade procedure, and the
versioning link talks about (initially) which version you should be
running. I'd break that into two Qs: "What's the upgrade procedure?"
(link to docs) and "What v
s like a poor optimisation to me.
A
--
Andrew Sullivan | [EMAIL PROTECTED]
The whole tendency of modern prose is away from concreteness.
--George Orwell
---(end of broadcast)---
TIP 9: In versions below 8.0, the planner will ignore you
er, be
trolling for registrants for the "Chinese" version of .mobi, which China
appears to be pressing ahead with in a split root that they're running.
A
--
Andrew Sullivan
Old sigs will return after re-constitution of blue smoke
---(end of broadcast)-
imited. It's been known to happen.
A
--
Andrew Sullivan
Old sigs will return after re-constitution of blue smoke
---(end of broadcast)---
TIP 2: Don't 'kill -9' the postmaster
his, but
if you're having specific problems, I think you need to talk to the people
who make the cluster software.
A
--
Andrew Sullivan
Old sigs will return after re-constitution of blue smoke
---(end of broadcast)---
TIP 3: Have you checked our extensive FAQ?
http://www.postgresql.org/docs/faq
On Thu, Dec 06, 2007 at 12:34:55PM +, srinath wrote:
> when i connecting my postgresql which giving
> org.postgresql.util.PSQLException: ERROR: conversion between UNICODE and
> MULE_INTERNAL is not supported.please send solution about this problem.
Sounds like you have your application
Sorry for this -- I hit the wrong key and approved rather than rejecting.
--
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-bugs
On Sun, Jun 01, 2008 at 10:27:25PM -0400, Tom Lane wrote:
> mode is pretty opaque :-(. I think the simplest solution is to reject
> non-absolute path for -X; is there any real use-case for allowing it?
No.
A
--
Andrew Sullivan
[EMAIL PROTECTED]
+1 503 667 4564 x10
imes to an inconsisten database
> with double primary keys in a table or a broken unique indexes (
> "pg_statistic_relid_att_index" for instance). I can't enforce this error.
I don't believe this is the problem you're having there. If what
you're saying i
is that "right clicking" happening? What interface are you
using? The delete is happening by _some_ command.
Anyway, you can do this with triggers. There's an example of doing
this in the manual, I believe.
A
--
Andrew Sullivan
[EMAIL PROTECTED]
+1 503 667 4564 x104
http://www.co
m. Reducing logging I've managed to restrict the
> error to the wee hours of the morning (at daily log rollover if the timing
> is just that perfect bad timing...) ..
This doesn't sound like a bug anyway. I'd post your issues on the
-general list and get some help
7. Might be worth trying on 8 as
well. If so, the FAQ should be updated so as not to limit the
discussion to Solaris 7 and earlier.
Sorry I can't be more help than this.
A
--
Andrew Sullivan 87 Mowat Avenue
Liberty RMS
27 matches
Mail list logo
