for a
PostgreSQL bug -- but we should fail gracefully, e.g. Use of prepared
statements with pgbench requires persistent connections. You may not
use the -C and -m prepared options together.
--
Josh Berkus
PostgreSQL Experts Inc.
http://pgexperts.com
--
Sent via pgsql-bugs mailing list (pgsql-bugs
: prepared statement P0_7 does not
exist
Client 2 aborted in state 7: ERROR: prepared statement P0_7 does not
exist
transaction type: TPC-B (sort of)
--
Josh Berkus
PostgreSQL Experts Inc.
http://pgexperts.com
--
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To make changes to your
have met with failure. So I'm filing this bug *in case* we see other
issues with repetitive RESET ROLE calls in the future.
--
Josh Berkus
PostgreSQL Experts Inc.
http://pgexperts.com
--
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To make changes to your subscription:
http
Folks,
So I'm a bit surprised that this bug report hasn't gotten a follow-up.
Does this sound like the known 9.2.2 corruption issue, or is it
potentially something else?
--
Josh Berkus
PostgreSQL Experts Inc.
http://pgexperts.com
--
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org
Alvaro,
BTW, we haven't been able to reproduce this crash deliberately, yet.
--
Josh Berkus
PostgreSQL Experts Inc.
http://pgexperts.com
--
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-bugs
On 03/08/2013 07:27 PM, Alvaro Herrera wrote:
Josh Berkus wrote:
Folks,
This is one I've never seen before:
= select generate_master_tables();
WARNING: AbortTransaction while in COMMIT state
PANIC: cannot abort transaction 9387287, it was already committed
Anything that causes
Mark,
I have PL/R and PL/v8 installed on that server (as well as a few other
extensions). However, neither of those is invoked in the procedure
which caused the crash; it's straight PL/pgSQL.
--
Josh Berkus
PostgreSQL Experts Inc.
http://pgexperts.com
--
Sent via pgsql-bugs mailing list
the range type for timestamptz. Why can't it?
--
Josh Berkus
PostgreSQL Experts Inc.
http://pgexperts.com
--
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-bugs
is not the normal failure for that.
Note that the tables were, in fact, created, and as far as I can tell
there's no corruption of the database.
--
Josh Berkus
PostgreSQL Experts Inc.
http://pgexperts.com
--
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To make changes to your subscription
| AccessExclusiveLock | test1
I understand why establishing an FK needs an ExclusiveLock on the
referenced table, but it doesn't need an AccessExclusiveLock. This
causes lots of deployment issues for users.
--
Josh Berkus
PostgreSQL Experts Inc.
http://pgexperts.com
--
Sent via pgsql-bugs mailing list
--
Josh Berkus
PostgreSQL Experts Inc.
http://pgexperts.com
--
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-bugs
on the log
collector for other reasons they can tweak this too, or when some new
hacker wants an easy first patch.
--
Josh Berkus
PostgreSQL Experts Inc.
http://pgexperts.com
--
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org
or directory
2012-04-26 16:38:21 PDT [10181]: [2-1] user=,db= LOG: disabling
automatic rotation (use SIGHUP to re-enable)
So, yes, exactly.
--
Josh Berkus
PostgreSQL Experts Inc.
http://pgexperts.com
--
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To make changes to your subscription
%';
schemaname | relname
+-
... so, apparently we still have an issue with cleaning up pg_toast_temp
schema?
--
Josh Berkus
PostgreSQL Experts Inc.
http://pgexperts.com
--
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To make changes to your subscription:
http
On 4/26/12 11:22 AM, Tom Lane wrote:
Josh Berkus j...@agliodbs.com writes:
summary: database has 291 empty pg_toast_temp schemas.
If your max_connections is 300 or more, this isn't surprising in the
least.
Yes, they are.
... so, apparently we still have an issue with cleaning up
On 4/26/12 3:48 PM, Tom Lane wrote:
Josh Berkus j...@agliodbs.com writes:
Also, have we discussed maybe hiding these schemas from \dn?
We've done more than discuss it:
http://git.postgresql.org/gitweb/?p=postgresql.gita=commitdiffh=e43fb604d6db229d70d3101aa53348cc16a5473a
I take it you're
of it.
I also tried a sighup to the logger process, with no effect.
--
Josh Berkus
PostgreSQL Experts Inc.
http://pgexperts.com
--
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-bugs
On 4/26/12 5:50 PM, Tom Lane wrote:
Josh Berkus j...@agliodbs.com writes:
Summary: despite pg_reload(), log directory, filename and destination
don't change
Looking at the code, it's really hard to see how this could possibly
happen, unless maybe the process is blocking receipt of SIGHUP
Do you want to try attaching to the collector with a debugger and seeing
if it ever gets into the if (got_SIGHUP) block in SysLoggerMain?
Hmmm. No debugger on this system, not unexpectedly. I'll see if I can
get authorization to add one.
--
Josh Berkus
PostgreSQL Experts Inc.
http
to the new location, and you change personnel; how
would the new DBA have any idea where the old log was so that he could
read the log message about the unwriteable directory?
--
Josh Berkus
PostgreSQL Experts Inc.
http://pgexperts.com
--
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org
On 1/28/12 5:27 PM, Tom Lane wrote:
Josh Berkus j...@agliodbs.com writes:
SUMMARY: if you attempt to UPDATE or DELETE FROM a parent table in an
inheritance relationship using a wCTE, you get the following error message:
ERROR: could not find plan for CTE
Fixed, thanks for the report
don't follow you at all Peter.
--
Josh Berkus
PostgreSQL Experts Inc.
http://pgexperts.com
--
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-bugs
, should ever cause that symptom, then it's, I
don't know what the terminology should be, say, a severe error.
+1
I'm strongly in favour of this.
This is *so* not a discussion to have on the pgsql-bugs list. Please
take it to -hackers.
--
Josh Berkus
PostgreSQL Experts Inc.
http
--
Josh Berkus
PostgreSQL Experts Inc.
http://pgexperts.com
--
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-bugs
The least painful solution might be to always quote *every* identifier
in commands sent to the source server, since we don't especially care
how nice-looking those are.
I've never been clear on why we don't do that in the first place.
--
Josh Berkus
PostgreSQL Experts Inc.
http
is getting mangled. Any
clue how?
--
Josh Berkus
PostgreSQL Experts Inc.
http://pgexperts.com
--
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-bugs
Seems you have a sequence called new; seems we don't handle that
well.
Hmmm ... yes, you're correct. Idiot users.
Interestingly, the sequence is no problem until 9.0. 8.4 handled it
fine. I'd guess this is another example of where merging in plpgsql
broke something.
--
Josh Berkus
and
later pg_dump does not. Any ideas?
--
Josh Berkus
PostgreSQL Experts Inc.
http://pgexperts.com
--
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-bugs
possible that this is something broken in the win1252
encoding itself. I've seen a lot of reports online for errors from
other software. However, we need to at least find a workaround for
users if we can't fix it ...
--
Josh Berkus
PostgreSQL Experts Inc.
http://pgexperts.com
--
Sent via pgsql
\copy is different because it uses OT_WHOLE_LINE mode to read the
argument, and that doesn't expand :variable references. I'd be a bit
leery of changing that.
So, doc warning then?
--
Josh Berkus
PostgreSQL Experts Inc.
http://pgexperts.com
--
Sent via pgsql-bugs mailing list (pgsql-bugs
with a default estimate
of 0.5.
I've tried to locate the cause of this problem, but the code involved is
rather convoluted and crusty, and I can't follow the logic. Help?
--
Josh Berkus
PostgreSQL Experts Inc.
http://pgexperts.com
--
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To make
On 9/21/11 1:56 PM, Tom Lane wrote:
Josh Berkus j...@agliodbs.com writes:
Summary: special inet operators ( = = ) are
up to 100X off in estimating rowcounts
A look in pg_operator will show you that these operators have no
associated selectivity estimators at all. It's not so
can't we estimate the
rowcount? Sorry if I'm being dense here, but I really don't understand
how the special operator code works at all.
--
Josh Berkus
PostgreSQL Experts Inc.
http://pgexperts.com
--
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To make changes to your
It's possible that we could build simple estimators for these operators
that just turn the problem into a range estimation and then pass it off
to somewhere else, but nobody has tried.
Right, that's why I'm asking. I'd like to reuse code ...
--
Josh Berkus
PostgreSQL Experts Inc.
http
perfectly fine with COPY. It's just \copy
which seems to be misbehaving.
--
Josh Berkus
PostgreSQL Experts Inc.
http://pgexperts.com
--
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-bugs
escaping characters on WIN1252.
The characters in question are also latin characters.
We've reproduced this on a clean install.
--
-- Josh Berkus
PostgreSQL Experts Inc.
http
a stack trace ...
--
-- Josh Berkus
PostgreSQL Experts Inc.
http://www.pgexperts.com
--
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To make changes to your subscription:
http
?
--
-- Josh Berkus
PostgreSQL Experts Inc.
http://www.pgexperts.com
--
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To make changes to your subscription:
http
On 3/3/11 2:31 PM, Josh Berkus wrote:
uname -a
Linux hemingway 2.6.32-25-server #44-Ubuntu SMP Fri Sep 17 21:13:39 UTC
2010 x86_64 GNU/Linux
date
Thu Mar 3 15:30:17 MST 2011
Also:
echo $TZ returns nothing. We've checked several Ubuntu systems, and it
seems that Ubuntu does not set $TZ
by a customer as a bug to us)
I'll give some thought as to how we could do so, and maybe add it to the
TODO list.
--
-- Josh Berkus
PostgreSQL Experts Inc.
http://www.pgexperts.com
--
Sent via
.
--
-- Josh Berkus
PostgreSQL Experts Inc.
http://www.pgexperts.com
--
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org
*that*.
--
-- Josh Berkus
PostgreSQL Experts Inc.
http://www.pgexperts.com
--
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql
On 1/26/11 12:13 PM, Tom Lane wrote:
Josh Berkus j...@agliodbs.com writes:
Oh! Actually, it only *did* 27 runs. So it actually completed building
the index. I'd expected trace_sort to give me some kind of completion
message; apologies for not checking all screen windows.
Huh
, using Sun CC
for the current test, I'm running with fsync off
(but I've had the same issue with fsync on)
Ideas?
(* object names have been changed to preserve confidentiality)
--
-- Josh Berkus
On 1/25/11 1:21 PM, Tom Lane wrote:
Josh Berkus j...@agliodbs.com writes:
Note: I have this running now on a test box. If someone responds in the
next couple hours, I can run whatever diagnostics you want on it.
Otherwise I'll kill it off and start over with debug logging turned
.
--
-- Josh Berkus
PostgreSQL Experts Inc.
http://www.pgexperts.com
--
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-bugs
was not compiled with support for SSL?
Exactly. If you don't get around to it, bug me in January.
--
-- Josh Berkus
PostgreSQL Experts Inc.
http://www.pgexperts.com
--
Sent via pgsql-bugs
if PostgreSQL was built with SSL support).
--
-- Josh Berkus
PostgreSQL Experts Inc.
http://www.pgexperts.com
--
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To make changes
: unrecognized configuration parameter ssl_ciphers
So, did ssl_ciphers go away on purpose? If so, why? If not, why isn't
it accessible?
--
-- Josh Berkus
PostgreSQL Experts Inc.
http
interface developers what this will break.
However, given that the issue has existed for a year or more and I'm the
first one to report it formally, it clearly isn't that huge of an issue.
Any idea what version this got broken in?
--
-- Josh Berkus
).
--
-- Josh Berkus
-
Josh Berkus PostgreSQL Experts Inc.
CEO database professionals
josh.ber...@pgexperts.com www.pgexperts.com
1-888-743-9778 x.508 San Francisco
an ORDER BY or not.
--
-- Josh Berkus
PostgreSQL Experts Inc.
http://www.pgexperts.com
--
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To make changes to your subscription
it now. If we include it in 9.0, we're stuck
with it for years.
I'm OK with forcing an initDB for RC1.
--
-- Josh Berkus
PostgreSQL Experts Inc.
http://www.pgexperts.com
--
Sent via pgsql
darned
solid pg_upgrade because of it.
--
-- Josh Berkus
PostgreSQL Experts Inc.
http://www.pgexperts.com
--
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To make changes
this, I get the following warning at
PostgreSQL startup time:
Loaded module auto_explain
Not safe to send CSV data
And on checking, auto-explain is indeed NOT sending anything to the
csvlog. It's not sending anything to the regular log, either.
--
-- Josh
On 7/7/10 1:50 AM, Magnus Hagander wrote:
BTW, if you post bug reports to -bugs, it'll make a lot more people see them.
Sure, we just want to verify that it *is* a possible bug (and not pilot
error) first.
--
-- Josh Berkus
Severity: minor
Tested On: 9.0b2, 8.4.4
Platform: SUN SPARC 4u Enterprise 450 Quad, presumably Solaris 10
Repeatable? Yes
Description:
See thread:
http://archives.postgresql.org/pgsql-testers/2010-06/msg00020.php
--
-- Josh Berkus
is the answer, given. Hmmm are
double-quotes respected in postgresql.conf, though? Need testing.
--
-- Josh Berkus
PostgreSQL Experts Inc.
http://www.pgexperts.com
--
Sent via pgsql
to restrict the number of rows output. A subselect in the
target list does not do so. However, that's completely another discussion.
--Josh Berkus
--
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-bugs
have an empty
array or a NULL in the 2nd column.
--
-- Josh Berkus
PostgreSQL Experts Inc.
http://www.pgexperts.com
--
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To make
On 4/5/10 9:16 PM, Josh Berkus wrote:
I can't see how this is anything but a bug; as far as I know, nothing in
the target list is allowed to restrict the number of rows which are
returned by the query. We should get 7 rows, 3 of which have an empty
array or a NULL in the 2nd column.
Just
should have succeeded. Or it
should have given a user-friendly error message. Opinions?
--Josh Berkus
--
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-bugs
That's better, I was worried you'd gone all complimentary on me.
grinNever fear that!
Was that setting originally part of your design for HS? If so, why did
you back off from it?
--Josh
--
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To make changes to your subscription:
at, it seems like a LOT of work.
--Josh Berkus
--
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-bugs
we should work on
making it less kludgy.
Ultimately we're going to need publish-XID-to-master, but that's not
realistic for 9.0.
--Josh Berkus
--
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-bugs
was incorrectly set in relation
pgbench_tellers page 1
... not one I'm familiar with. Issues?
--Josh Berkus
--
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-bugs
of that.
--Josh Berkus
--
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-bugs
All,
I tested Noel's test case and verified that it does, in fact, break.
And functions on 8.4.
--Josh Berkus
Original Message
Subject: [TESTERS] Numerics of diffrent scales Raises Type Mismatch
Error in a Set Returning Function
Date: Tue, 2 Mar 2010 20:07:07 -0800
From: Noel
Pavel, all:
Apparently if you use one returns table function to call a 2nd returns
table function, it returns a recordset which consists entirely of nulls.
Here's the test case:
create table srf_data ( id serial, cat int, val text );
insert into srf_data ( cat, val ) values
( 1, 'josh' ),
( 1,
val1 is just as ambiguous. I think you got bit by the name collision;
the output parameters would start out NULLs and thus lead to the
described behavior, in versions before 9.0.
Aha, yeah, that's probably it. Take this example as the reason we had
to change the behavior ...
--Josh Berkus
It's too bad you didn't capture a stack backtrace at step #3 or step
#6. If you manage to reproduce the problem, that would be a good
thing to try to get.
It never actually crashed. And, of course, this was happening right
when I needed to go home and the server needed to be up for that.
can mine out of the logs or files?
--Josh Berkus
--
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-bugs
in this matter.
Um, there's no such thing as PostgreSQL 8.7.3. The latest stable
version is *8.3.7*. Was that the version you meant?
If that's the case, then everything you want is here:
http://www.postgresql.org/download/linux
http://www.postgresql.org/ftp/source/v8.3.7/
--Josh Berkus
--
Sent
Tom Lane wrote:
Josh Berkus j...@agliodbs.com writes:
When doing pg_dump in text mode, complext types will be dumped like this:
CREATE TYPE complex_foo (
var INT,
gar TEXT,
natch public.foo_type
);
You didn't say which schema complex_foo is in?
Public
Jeff Davis wrote:
On Fri, 2009-02-27 at 01:24 -0500, Tom Lane wrote:
Are you entirely sure that they don't?
Oh, you're right, of course:
postgres=# create type public.mytype as (i int);
CREATE TYPE
postgres=# create type public.mytype2 as (j mytype);
CREATE TYPE
-- pg_dump output:
CREATE
schema_path. This is inconsistent with all other database objects,
which use SET search_path to qualify the correct schemas.
This is only a real problem in that it may interfere with backup and/or
schema comparison automation (like I'm trying to write right now).
--Josh Berkus
--
Sent via
Jeff,
Functions are similar, actually. The argument list needs to specify
schema paths as well, if it's not in some expected place (I think it
does so for all schemas other than pg_catalog).
Except that they don't appear to do so.
--Josh
--
Sent via pgsql-bugs mailing list
public is also excluded as well as
pg_catalog. For CREATE TYPE, public is explicit.
Have you considered working from the custom format rather than text?
I'm not sure whether it solves your problem, but I think it provides the
most information.
--Josh Berkus
--
Sent via pgsql-bugs mailing list
that
the trigger should *fail*, with an error. Not work.
Throughout the history of the project, no functionality which ends in a
inconsistent data state has ever been acceptable which I can recall.
When did we change our policy?
--Josh Berkus
--
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org
Version: 8.3.5
Install: self-compile on 64-bit Ubuntu Linux
also reproduced by AndrewSN on another platform
Summary: self-referential FKs are not enforced properly in the
presence of BEFORE triggers
Test Case:
-- create two tables, one of which is the master table (reftable) the
Tom Lane wrote:
Josh Berkus j...@agliodbs.com writes:
Summary: self-referential FKs are not enforced properly in the
presence of BEFORE triggers
This isn't a bug. If you create triggers that prevent the RI actions
from being taken, it's your own problem.
Huh? Since when was it OK
unambiguously.
Ok, so yes, it's inconsistent, but we don't want to break backwards
compatibility. I can buy that ...
--
--Josh
Josh Berkus
PostgreSQL @ Sun
San Francisco
---(end of broadcast)---
TIP 2: Don't 'kill -9' the postmaster
tarr[1] from test_arr;
tarr
--
xy
(1 row)
scratch=# select tarr[2] from test_arr;
tarr
--
x\y
(1 row)
--
--Josh
Josh Berkus
PostgreSQL @ Sun
San Francisco
---(end of broadcast)---
TIP 9: In versions below 8.0, the planner will ignore
| name | is_true
++-
1 | Before ALTER |
2 | Look, its null | t
3 | Now its true. | t
--
--Josh
Josh Berkus
Aglio Database Solutions
San Francisco
create table bugtest (
id serial not null primary key,
name text not null unique
);
create function
.
--
Josh Berkus
Aglio Database Solutions
San Francisco
---(end of broadcast)---
TIP 6: explain analyze is your friend
, $2 [ $3 ] )
PL/pgSQL function generate_test_series line 67 at SQL statement
ERROR: relation with OID 16607 does not exist
This is CVS as of a week ago.
--
--Josh
Josh Berkus
Aglio Database Solutions
San Francisco
---(end of broadcast
CVS, the day before the beta release. Ignore me if it's
already been fixed.
--
--Josh
Josh Berkus
Aglio Database Solutions
San Francisco
---(end of broadcast)---
TIP 9: In versions below 8.0, the planner will ignore your desire to
choose
notes:
WARNING: 8.1's psql is not completely backwards-compatible with previous
versions of PostgreSQL.
--Josh
--
__Aglio Database Solutions___
Josh BerkusConsultant
josh@agliodbs.comwww.agliodbs.com
Ph: 415-752-2500Fax: 415-752-2387
2166 Hayes
wants to shut you down ...
Well, I can run an actual timer if you like. But it's definitely more than
20 seconds. And we're using the default bgwriter config, perhaps I should
set it to 0?
--
Josh Berkus
Aglio Database Solutions
San Francisco
---(end of broadcast
. Is there some way for pg_ctl to intelligently detect
this situation? To set a timeout value for pg_ctl via a command-line
option?
--
--Josh
Josh Berkus
Aglio Database Solutions
San Francisco
---(end of broadcast)---
TIP 8: explain analyze is your friend
Brian,
They PGSQL-PERFORMANCE list is really the appropriate place for performance
issues like yours. Subscribe?
http://www.postgresql.org/community/lists
--
--Josh
Josh Berkus
Aglio Database Solutions
San Francisco
---(end of broadcast
read the performance
list.
--
--Josh
Josh Berkus
Aglio Database Solutions
San Francisco
---(end of broadcast)---
TIP 7: don't forget to increase your free space map settings
felt that the SQL committee made a mistake
in having aggregates of no rows produce a single null output row; it leads to
wierdness like this here.
Hopefully someone can back that up with an ANSI-SQL reference ...
--
Josh Berkus
Aglio Database Solutions
San Francisco
| 0 | 5 | 0 | 0
--
--Josh
Josh Berkus
Aglio Database Solutions
San Francisco
---(end of broadcast)---
TIP 3: if posting/reading through Usenet, please send an appropriate
subscribe-nomail command to [EMAIL
trouble stems from trying to coerce the
first into the second.
Maybe it's time to hack a datatype ...
--
--Josh
Josh Berkus
Aglio Database Solutions
San Francisco
---(end of broadcast)---
TIP 8: explain analyze is your friend
or GMT for both.
--Josh Berkus
P.S. if anyone is wondering why I'm doing epoch with timestamp-no-tz it's for
a calendaring application which exists on 2 servers in two different time
zones, and all I really want is the date.
---(end of broadcast
protects some ports. Please see the service pack documentation, and make
sure that you have opened port 5432, and re-test.
--
--Josh
Josh Berkus
Aglio Database Solutions
San Francisco
---(end of broadcast)---
TIP 2: you can get off all lists
thought I should raise
this issue ASAP.
--
--Josh
Josh Berkus
Aglio Database Solutions
San Francisco
---(end of broadcast)---
TIP 6: Have you searched our list archives?
http://archives.postgresql.org
Folks,
I'm finding an issue I thought was fixed with RC2, which is affecting my
ability to use arrays in RC5:
Oh, this may be a bug specifically in INTARRAY; that module is installed.
--
--Josh
Josh Berkus
Aglio Database Solutions
San Francisco
---(end of broadcast
to specific ports -- particularly 5432.
--
Josh Berkus
Aglio Database Solutions
San Francisco
---(end of broadcast)---
TIP 9: the planner will ignore your desire to choose an index scan if your
joining column's datatypes do not match
1 - 100 of 171 matches
Mail list logo
