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
at one should always use SvOK() to
check for undef. IIRC some SvOK() tests were added in some places where
it was found to be necessary, and the old tests kept out of an abundance
of caution, but a little googling suggests that you are correct.
cheers
andrew
---
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
ples=%d, err=%s, res_err=%s\n",
PQntuples(res),
PQerrorMessage(conn),
PQresultErrorMessage(res));
PQclear(res);
PQfinish(conn);
return 0;
}
andrew
---(end of broadcast)---
TIP 5: don't forget to increase your free space map settings
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
I don't recall making such a conscious intention - not sure about others
whose fingers have been in the pie. More likely it's just oversight. In
general, I'd say that the log content should be independent of the
format. I can't see any very good reason for text logs to have
Tom Lane wrote:
Andrew Dunstan <[EMAIL PROTECTED]> writes:
I can't see any very good reason for text logs to have different
content from CSV logs.
Well, if we want to cram all that stuff in there, how shall we do it?
It seems wrong to put all those lines into one text fie
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
Tom Lane wrote:
Andrew Dunstan <[EMAIL PROTECTED]> writes:
Tom Lane wrote:
Well, if we want to cram all that stuff in there, how shall we do it?
It seems wrong to put all those lines into one text field, but I'm
not sure I want to add six more text fields to the CSV fo
Tom Lane wrote:
Andrew Dunstan <[EMAIL PROTECTED]> writes:
Tom Lane wrote:
One issue here is that CONTEXT is potentially multiple lines. I'm not
sure that there is much we can do about that, especially not at the last
minute. If we had some time to rewrite internal APIs
Alvaro Herrera wrote:
Andrew Dunstan wrote:
OK, works for me. I'll try to look at it after I have attended to the
Windows build issues. My plate is pretty full right now, though.
FYI I'm having a look at it now.
Great. Thanks.
cheers
andrew
-
Alvaro Herrera wrote:
Tom Lane wrote:
Andrew Dunstan <[EMAIL PROTECTED]> writes:
Tom Lane wrote:
Well, if we want to cram all that stuff in there, how shall we do it?
It seems wrong to put all those lines into one text field, but I'm
not sure I want to add si
The following bug has been logged online:
Bug reference: 3866
Logged by: Andrew Gilligan
Email address: [EMAIL PROTECTED]
PostgreSQL version: 8.3RC1
Operating system: FreeBSD 4.11
Description:Segfault during table update when using convert_from()
Details:
Greetings
On 9 Jan 2008, at 23:45, Tom Lane wrote:
"Andrew Gilligan" <[EMAIL PROTECTED]> writes:
It seems there exists a bug in the way character set conversion
is handled in some circumstances.
Seems to be the bogus pfree() in pg_convert_from() that's causing
the problem :-(.
The following bug has been logged online:
Bug reference: 3921
Logged by: Andrew Gilligan
Email address: [EMAIL PROTECTED]
PostgreSQL version: 8.3.0
Operating system: FreeBSD 4.11
Description:CREATE TABLE / INCLUDING INDEXES fails with permission
denied
Details:
Hi
he forward slashes to backslashes at the top[
of that loop it should work, but haven't had time to test.
cheers
andrew
---(end of broadcast)---
TIP 4: Have you searched our list archives?
http://archives.postgresql.org
Magnus Hagander wrote:
I have a patch working for me, I've sent it over to Gevik for testing in
his environment. Attached here if somebody else wants to play.
Looks OK.
cheers
andrew
---(end of broadcast)---
TIP 4: Have you searche
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
o.com/
andrew
--
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-bugs
good idea. I just don't
think it solves any of the interesting problems.
--
Andrew Chernow
eSilo, LLC
every bit counts
http://www.esilo.com/
--
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-bugs
documentation and possibly how
tedious of an API call PQexecParams can be. If anything, using the
parameterized method promotes much better "safer" coding practices, but
currently its at quite a programming effort cost.
--
Andrew Chernow
eSilo, LLC
every bit counts
http://www.esilo.com
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
I am able and
this appears not to have changed.
Regards,
Andrew.
--
--------
Andrew @ Catalyst .Net.NZ Ltd, PO Box 11-053, Manners St, Wellington
WEB: http://catalyst.net.nz/PHYS: Level 2
On Tue, 2002-05-28 at 04:59, Tom Lane wrote:
> Andrew McMillan <[EMAIL PROTECTED]> writes:
> > Reading between a few lines I got the impression that the manual
> > suggested something like:
> > CREATE or REPLACE myfunc( tablename%ROWTYPE ) RETURNS ...
> > When I f
s of
use of tablename as a parameter, %ROWTYPE and %TYPE.
In the end I decided that the documentation is literally correct, but
hard to follow without any examples explicitly showing the use of a
table name as a parameter.
Cheers,
rds,
Andrew.
>
> Sam
>
> -Original Message-
> From: Sam Liddicott
> Sent: 31 May 2002 10:57
> To: '[EMAIL PROTECTED]'
> Subject: drop tempoary table VERY slow
>
>
> I have a DB where this:
>
> select 1 into tempo
perhaps less interesting while you
are running your current solution - maybe a comparison would be
worthwhile.
Regards,
Andrew.
--
Andrew @ Catalyst .Net.NZ Ltd, PO Box 11-053, Manners St,
side that you then:
REINDEX DATABASE ;
Once it is done, quit and restart your database.
Regards,
Andrew.
--
Andrew @ Catalyst .Net.NZ Ltd, PO Box 11-053, Manners St, Wellington
WEB: http://catalyst.net.nz/PHY
ell script I found out why:
PGDUMP="${PGPATH}/pg_dump $connectopts $pgdumpextraopts -Fp"
Is there a particular reason why plain text is forced? Could this be removed
in the next version? Or even moved to a pg_dumpall command line option? I
really dislike using nonstandard tools.
Re
henever foreign keys can be across
databases?
Regards,
Andrew
---(end of broadcast)---
TIP 2: you can get off all lists at once with the unregister command
(send "unregister YourEmailAddressHere" to [EMAIL PROTECTED])
who think they want that
> actually want cross-schema operations, which will work fine in 7.3.
Thank you for your time and comments. I feel a lot "safer" about these
backups now.
Regards,
Andrew
---(end of broadcast)---
TIP 2: yo
't able to turn up
any evidence that it happened on Solaris 8. But it might. We don't
use 8, at least not yet.
> Andrew, I think that was your test case we found it on. Do you
> recall if a fix is available from Sun?
Not as far as I know, at least for 7. Come to think of it,
ot;MyTable" - different (i.e. "MyTable").
In converting from SQL Server you probably want to either ensure all
identifiers are always quoted, or that they never are. Hopefully you
don't have table names that need to be "MyTab
L compliant on this issue.
Regards,
Andrew.
--
-----
Andrew @ Catalyst .Net.NZ Ltd, PO Box 11-053, Manners St, Wellington
WEB: http://catalyst.net.nz/ PHYS: Level 2, 150-154 Willis St
DDI: +64(4)916-7201 MOB: +64(2
Filter: (uid = $0)
As you can see, optimizer in earlier version of PostgreSQL skips
unneeded data, but latest version doesn't.
This behavior can slow down query execition, especially if subselect is
time consuming and rarely used.
--
with best wishes
Andrew KoshelevSystem
I think there should be a default that works if you say
to_number(variable);
(ie no format string) regardless of the locale.
I am a new user, and assumed it was my mistake for a good 6 hours
of experimenting :-(
Andrew
---(end of broadcast)--
row)
golem=> update nametable set names = '{"arf"}' where id = 1;
UPDATE 1
golem=> select id, names from nametable where id = 1;
id | names
+--
1 | {arf}
(1 row)
I'll be glad to document this further if needed.
---
Andrew C. Esh
I was able to do this test on a platform running 7.3.2, and the result is the same as
version 7.4.1, so if this is a bug, it is also in version 7.3.2.
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] Behalf Of Esh, Andrew
Sent: Thursday, January 08, 2004 12:53 PM
To
unsubscribe
---(end of broadcast)---
TIP 3: if posting/reading through Usenet, please send an appropriate
subscribe-nomail command to [EMAIL PROTECTED] so that your
message can get through to the mailing list cleanly
could
contemplate running *any* server on FAT. But then, people use Notepad to
write programs, too.
The installer should complain, but I guess that's it.
cheers
andrew
---(end of broadcast)---
TIP 1: subscribe and unsubscribe commands go to [EMAIL PROTECTED]
QUERY, and it
takes about 15 mins to look it up!. (Even after using SQL for nearly 20
years :-()
regards
Andrew
---(end of broadcast)---
TIP 5: Have you checked our extensive FAQ?
http://www.postgresql.org/docs/faqs/FAQ.html
entirely.
Of course you are superuser when you review such logs, but I wouldn't
usually want the db connection from the application to have to run as
superuser if I could help it... especially not a web application.
Regards,
Andrew McMillan.
---
d just set
perl_embed_ldflags to the output of `perl -MExtUtils::Embed -e ldopts`.
--
Andrew, Supernews
http://www.supernews.com - individual and corporate NNTP services
---(end of broadcast)---
TIP 5: Have you checked our extensive FAQ?
http://www.postgresql.org/docs/faqs/FAQ.html
On 2004-11-16, Tom Lane <[EMAIL PROTECTED]> wrote:
> Andrew - Supernews <[EMAIL PROTECTED]> writes:
>> As I originally said in IRC, I do not know why the configure script is
>> trying to second-guess the ExtUtils::Embed output; however, what it is
>> doing c
talk about providing macros
> for more flexible specification of rpath, so we can fix the problem if
> we can get the Perl library path, but I'm unsure where to learn that.
Oddly enough, that's what ccdlflags is for. So you'd end up removing that
info from ldopts only to add
hich was the
only other place I found where constraint_name is used without any table
name being present. I don't know what the spec says, but it seems that
something is assuming that constraint_name is unique within the schema,
which of course is not the case in the above example.
--
Andrew, S
L_LOCAL_APPDATA.
I think CSIDL_APPDDATA is probably the way to go, but one of the heavy
Windows hitters will know better than I do.
cheers
andrew
---(end of broadcast)---
TIP 5: Have you checked our extensive FAQ?
http://www.postgresql.org/docs/faqs/FAQ.html
s the permissions are 0700 ). If that isn't enough on
Windows, perhaps someone can tell us what is.
cheers
andrew
---(end of broadcast)---
TIP 4: Don't 'kill -9' the postmaster
The following bug has been logged online:
Bug reference: 1387
Logged by: Andrew Kompaneev
Email address: [EMAIL PROTECTED]
PostgreSQL version: 8.0 RC2
Operating system: Windows 2000 SP4
Description:Sort order don't work correctly
Details:
On Windows platfo
The following bug has been logged online:
Bug reference: 1399
Logged by: Andrew Lazarus
Email address: [EMAIL PROTECTED]
PostgreSQL version: 8
Operating system: Not applicable
Description:web site problem
Details:
Your new light blue text on the home page is
fixing this:
1) change the semantics of &< and &> to match rtree's expectations
2) replace &< and &> in the opclass with operators that behave as rtree
expects (this will have the side effect of rendering &< and &> un-indexable)
3) change rtree's
On 2005-01-25, Tom Lane <[EMAIL PROTECTED]> wrote:
> Andrew - Supernews <[EMAIL PROTECTED]> writes:
>> The problem is that the semantics of the &< and &> operators for the box
>> type are not what rtree needs for the "OverLeft" and "OverRigh
The following bug has been logged online:
Bug reference: 1486
Logged by: Andrew Gold
Email address: [EMAIL PROTECTED]
PostgreSQL version: 7.4.7
Operating system: Debian Linux
Description:Apostrophes are not ignored in pgplsql comments
Details:
In pgplsql functions
The following bug has been logged online:
Bug reference: 1542
Logged by: Andrew Slobodyanyk
Email address: [EMAIL PROTECTED]
PostgreSQL version: 8.0.1
Operating system: linux 2.4.26, gcc 3.2.2
Description:pg_dump seg fault
Details:
After power failure any operation
> Hmmm. What did you do to "delete that table" exactly? The crash
To tell the truth, I delete the table using Windows PgAdmin. I guess it has
done the same operation, hasn't it?
> suggests that there is a row in pg_rewrite that links to a nonexistent
> row in pg_class. It'd be better if pg_dump
f
constraints until after the data load (which can be quite inconvenient in
some cases).
--
Andrew, Supernews
http://www.supernews.com - individual and corporate NNTP services
---(end of broadcast)---
TIP 7: don't forget to increase your free space map settings
pin that
down to the same problem (especially since such a restore should be filling
the referenced table before the referencing table).
--
Andrew, Supernews
http://www.supernews.com - individual and corporate NNTP services
---(end of broadcast)
because when the first insert happens
on a referencing table, there will be no reason for the planner to prefer
a sequential scan. So this result is not surprising at all.
--
Andrew, Supernews
http://www.supernews.com - individual and corporate NNTP services
--
On 2005-03-23, Tom Lane <[EMAIL PROTECTED]> wrote:
> Andrew - Supernews <[EMAIL PROTECTED]> writes:
>> Changing the order so that the referenced table is fully populated, or at
>> least populated with more than a handful of pages of rows, before doing
>> _any_ ins
(easily fitting in
one page) that index scans are as fast as or faster than seqscans for
doing simple one-row lookups provided the tables are in cache.
--
Andrew, Supernews
http://www.supernews.com - individual and corporate NNTP services
---(end of broadcast)-
or the merge join, but it appears to
be reducing its total cost estimate below that of the child nodes on the
assumption that the join can be aborted early, which is clearly not the
case for outer joins.
--
Andrew, Supernews
http://www.supernews.com - individual and corpor
The following bug has been logged online:
Bug reference: 1583
Logged by: Andrew Grillet
Email address: [EMAIL PROTECTED]
PostgreSQL version: 7.4.7
Operating system: FreeBSD 5.3
Description:Locale problem
Details:
error message XX000: cannot assign "" to L
# create function crashme() returns text as 'select timeofday()'
test-# language sql stable;
CREATE FUNCTION
test=# begin;
BEGIN
test=# declare t cursor with hold for select crashme() as x from pg_class;
DECLARE CURSOR
test=# commit;
server closed the connection unexpectedly
--
Andrew,
if (pc->flags & TOASTED)
(that test could be moved into the setup phase, of course)
--
Andrew, Supernews
http://www.supernews.com - individual and corporate NNTP services
---(end of broadcast)---
TIP 1: subscribe and unsubscribe commands go to [EMAIL PROTECTED]
(not timestamptz) which
causes the other version of age() to be used instead. So this is obviously
a timezone-related issue. Couldn't reproduce on 8.0.1 with any timezone.
--
Andrew, Supernews
http://www.supernews.com - individual and corporate NNTP services
---(end of broadcast)---
TIP 4: Don't 'kill -9' the postmaster
On 2005-04-29, Tom Lane <[EMAIL PROTECTED]> wrote:
> Andrew - Supernews <[EMAIL PROTECTED]> writes:
>> I did some analysis for this one when it was mentioned just now in the irc
>> chan. I can reproduce on 7.4.x as follows:
>
>> test=> set timezone to
the
Unix standards clearly specify that sockaddr_storage must be both sized
and aligned such that a sockaddr_* struct for any supported protocol
can be stored there.
See the entry for in the Headers chapter of the
Base Definitions volume of the SUSv3.
--
Andrew, Supernews
htt
The following bug has been logged online:
Bug reference: 1665
Logged by: Andrew Fabbro
Email address: [EMAIL PROTECTED]
PostgreSQL version: 8.0.3
Operating system: Any
Description:postgresql-8.0.3.zip corrupt
Details:
I downloaded the Win32 distribution postgresql
that in due
course)
The reason for the hang is that the sending end of the pipe from initdb
to postgres is not being closed by popen(), so postgres never sees EOF
on it. In this context I am suspicious of the fact that while libpq is
being built with threading, the apps which link against it do
On 2005-05-21, Tom Lane <[EMAIL PROTECTED]> wrote:
> Andrew - Supernews <[EMAIL PROTECTED]> writes:
>> The reason for the hang is that the sending end of the pipe from initdb
>> to postgres is not being closed by popen(), so postgres never sees EOF
>> on it. In th
On 2005-05-21, Tom Lane <[EMAIL PROTECTED]> wrote:
> Andrew - Supernews <[EMAIL PROTECTED]> writes:
>> On 2005-05-21, Tom Lane <[EMAIL PROTECTED]> wrote:
>>> initdb does not use libpq ... it might link to it,
>
>> Linking to it is enough to bring in l
estamp value in the
database is stored, it's hard to see how it could be made switchable at
runtime.
--
Andrew, Supernews
http://www.supernews.com - individual and corporate NNTP services
---(end of broadcast)---
TIP 3: if posting/reading t
ly
where function calls are involved and major optimizations can be made on
constant values as a result of inlining.
--
Andrew, Supernews
http://www.supernews.com - individual and corporate NNTP services
---(end of broadcast)---
TIP 3: if posting/r
On 2005-07-06, Oliver Jowett <[EMAIL PROTECTED]> wrote:
> Andrew - Supernews wrote:
>> The problem is that even with the unnamed statement and deferred planning,
>> the planner still has to treat the parameters as variables, not constants,
>> since nothing in the prot
The following bug has been logged online:
Bug reference: 1781
Logged by: Andrew Smith
Email address: [EMAIL PROTECTED]
PostgreSQL version: 7.4.6
Operating system: Debian GNU/Linux 3.1
Description:result of cascading triggers not available until
function exits
her the WHERE clause of a rule will
be matched, so the rule is always expanded the same way, and the WHERE
clause becomes part of the rewritten command.
--
Andrew, Supernews
http://www.supernews.com - individual and corporate NNTP services
---(end of broadcast)-
the (not
inconsiderable) amount of work needed to implement it, since the performance
overhead of copying the data via the socket instead is not a large factor
in the overall cost of a large copy.
--
Andrew, Supernews
http://www.supernews.com - individual and corporate NNTP services
-
t;>> test(> '2005-10-29 13:22:00-04'::timestamptz);
>>> ?column?
>>> --
>>> 25:00:00
>>> (1 row)
>
>> Is that actually the correct answer?
>
> I'm of the opinion that the correct answer, or at least the usually
m, what? Under what conditions is it permissable for simple arithmetic on
(only) timestamptz values (which may have originated in different timezones
neither of which is the current one) to be dependent on the current timezone
setting?
--
Andrew, Supernews
http://www.supernews.com - indiv
ifference is that a user in US/Eastern might, under
some circumstances, wish to regard that time period as '1 day' rather
than 25 hours; no user in any other timezone would do so. Since the
conversion from '25 hours' to '1 day' loses information, it should not
On 2005-10-26, Tom Lane <[EMAIL PROTECTED]> wrote:
> Andrew - Supernews <[EMAIL PROTECTED]> writes:
>> Um, what? Under what conditions is it permissable for simple arithmetic on
>> (only) timestamptz values (which may have originated in different timezones
>> ne
\ as the text delimiter.
Maybe ERRCODE_INVALID_PARAMETER_VALUE ? Or maybe we need a new one.
Also, I would probably make the format %#.02x so the result would look
like 0x0d (for a CR).
(I bet David never thought there would so much fuss over a handful of
lines of code)
cheers
andrew
-
/* Don't allow the delimiter to appear in the null string. */
>if (strchr(cstate->null_print, cstate->delim[0]) != NULL)
>ereport(ERROR,
>(errcode(ERRCODE_FEATURE_NOT_SUPPORTED),
>errmsg("COPY delimiter must not appear in the NULL
>
imate is larger than this, a hashed subplan will not be used since
it does not spill to disk; instead it will use a plain subplan.
Rewrite the query as an outer join and you will be much better off.
--
Andrew, Supernews
http://www.supernews.com - individual and corporate NNTP services
On Mon, 13 Feb 2006, Tom Lane wrote:
> Andrew Klosterman <[EMAIL PROTECTED]> writes:
> > I threw in a pthread mutex around the code making the database connections
> > for each of my threads. The problem is still there ("corrupted
> > double-linked list"
On Mon, 13 Feb 2006, Tom Lane wrote:
> Andrew Klosterman <[EMAIL PROTECTED]> writes:
> > (gdb) bt
> > #0 0x401c3851 in kill () from /lib/libc.so.6
> > #1 0x40139dd5 in EF_Abort () from /usr/lib/libefence.so.0
> > #2 0x40139823 in memalign () from /usr/lib/lib
-compiled code,
for my postgres installation. From the information I can gather from the
debian build logs (http://buildd.debian.org/build.php), everything was
configured and built with threads enabled.
--Andrew J. Klosterman
[EMAIL PROTECTED]
---(end of broadcast)---
TIP 6: explain analyze is your friend
101 - 200 of 260 matches
Mail list logo
