On Fri, Nov 19, 2004 at 05:15:54PM +1300, Dru wrote:
I'll get the developer to write down the exact error when it happens again.
It would be better to cut and paste the error message instead of
writing it down. What people think they see doesn't always match
what's on the screen.
--
Michael
the connection unexpectedly
--
Michael Fuhr
http://www.fuhr.org/~mfuhr/
---(end of broadcast)---
TIP 5: Have you checked our extensive FAQ?
http://www.postgresql.org/docs/faqs/FAQ.html
---+---
1 | 2
3 | 4
(2 rows)
CREATE FUNCTION foo_bad() RETURNS SETOF footype AS $$
return [
[1, 2],
[3, 4]
];
$$ LANGUAGE plperl;
SELECT * FROM foo_bad();
server closed the connection unexpectedly
--
Michael Fuhr
http://www.fuhr.org/~mfuhr/
---(end of broadcast
: list of hashes expected, hash value not scalar
CREATE FUNCTION test9() RETURNS SETOF footype AS $$
return [{txtval = [test 1], intval = 42}];
$$ LANGUAGE plperl;
SELECT * FROM test9();
txtval | intval
--+
ARRAY(0x8438d74) | 42
(1 row)
--
Michael Fuhr
tests.
--
Michael Fuhr
http://www.fuhr.org/~mfuhr/
---(end of broadcast)---
TIP 7: don't forget to increase your free space map settings
a.out
a.out: ELF 64-bit MSB executable SPARCV9 Version 1, dynamically
linked, not stripped
--
Michael Fuhr
http://www.fuhr.org/~mfuhr/
---(end of broadcast)---
TIP 9: the planner will ignore your desire to choose an index scan if your
?
--
Michael Fuhr
http://www.fuhr.org/~mfuhr/
---(end of broadcast)---
TIP 2: you can get off all lists at once with the unregister command
(send unregister YourEmailAddressHere to [EMAIL PROTECTED])
On Tue, Nov 23, 2004 at 11:34:44AM -0700, Michael Fuhr wrote:
gcc 3.4.2 on Solaris 9/sparc 64 appears to be okay.
But gcc 3.3.2 on Solaris 9/sparc 64 isn't.
% gcc -m64 test.c
% ./a.out
x = 12.3
y = 12.3
% gcc -O -m64 test.c
% ./a.out
x = 12.3
y = 2.51673e-42
% gcc -O2 -m64 test.c
% ./a.out
then please be more specific.
--
Michael Fuhr
http://www.fuhr.org/~mfuhr/
---(end of broadcast)---
TIP 6: Have you searched our list archives?
http://archives.postgresql.org
On Tue, Nov 23, 2004 at 10:46:54PM -0700, Michael Fuhr wrote:
On Thu, Nov 23, 2000 at 11:59:58AM +0800, Arnold.Zhu wrote:
Ummm...did you know your clock was four years behind?
--
Michael Fuhr
http://www.fuhr.org/~mfuhr/
---(end of broadcast
on my (t)rusty ol' Ultra 1.
--
Michael Fuhr
http://www.fuhr.org/~mfuhr/
---(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
On Wed, Dec 01, 2004 at 08:10:24PM -0700, Michael Fuhr wrote:
Don't know about Solaris 9/sparc yet -- the whole dance takes over
an hour on my (t)rusty ol' Ultra 1.
Solaris 9/sparc passes all tests.
--
Michael Fuhr
http://www.fuhr.org/~mfuhr/
---(end of broadcast
CONTEXT: PL/pgSQL function foo
SELECT foo(3);
INFO: before CONTINUE: i = 1
INFO: before CONTINUE: i = 2
INFO: before CONTINUE: i = 3
INFO: after CONTINUE: i = 3
foo
-
3
(1 row)
--
Michael Fuhr
http://www.fuhr.org/~mfuhr/
---(end of broadcast
the corresponding fixes in contrib/rtree_gist as well.
Excellent. If the fix is straightforward, is it going to be
backpatched at least to 8.0? Or is backpatching not worthwhile,
considering that hardly anybody stumbles across the problem or
complains about it?
--
Michael Fuhr
http://www.fuhr.org/~mfuhr
On Sat, Jun 18, 2005 at 05:27:28PM +0200, Tino Wildenhain wrote:
Am Samstag, den 18.06.2005, 08:41 -0600 schrieb Michael Fuhr:
I was going to submit a patch, but I don't know enough about the
Python API or how Python and PostgreSQL handle Unicode to know
whether adding that simple check
fair game, but GetConfigOptionByName() (declared
in utils/guc.h) appears to work. Can any of the developers comment
on whether it's appropriate for user-defined code to call this
function?
--
Michael Fuhr
http://www.fuhr.org/~mfuhr/
---(end of broadcast
directory data
I saw Tom's comment about many loose ends remaining -- is this one
of them?
--
Michael Fuhr
http://www.fuhr.org/~mfuhr/
---(end of broadcast)---
TIP 3: if posting/reading through Usenet, please send an appropriate
subscribe
was that
it's due to a bug in AIX:
http://archives.postgresql.org/pgsql-bugs/2005-05/msg00072.php
http://archives.postgresql.org/pgsql-bugs/2005-05/msg00085.php
http://archives.postgresql.org/pgsql-bugs/2005-05/msg00090.php
--
Michael Fuhr
http://www.fuhr.org/~mfuhr
, this thread probably doesn't belong on pgsql-hackers, at least
not yet.
--
Michael Fuhr
http://www.fuhr.org/~mfuhr/
---(end of broadcast)---
TIP 2: you can get off all lists at once with the unregister command
(send unregister YourEmailAddressHere
for one person asking about
it last year:
http://archives.postgresql.org/pgsql-admin/2004-12/msg00065.php
--
Michael Fuhr
http://www.fuhr.org/~mfuhr/
---(end of broadcast)---
TIP 3: if posting/reading through Usenet, please send an appropriate
On Sun, Jul 03, 2005 at 04:24:31PM +1000, Russell Smith wrote:
On Sun, 3 Jul 2005 03:32 pm, Michael Fuhr wrote:
I've noticed that contrib/pgcrypto/pgcrypto.sql.in doesn't include
a volatility category in its CREATE FUNCTION statements, so the
functions are all created VOLATILE. Shouldn't
On Sun, Jul 03, 2005 at 03:59:51PM +0300, Marko Kreen wrote:
On Sun, Jul 03, 2005 at 12:43:32AM -0600, Michael Fuhr wrote:
Yeah, I see that gen_salt() needs to be volatile, but I was thinking
about functions like digest(), encrypt(), decrypt(), etc., that
would be expected to return
Notes could mention that recreating
the functions is required; it could also show the SQL statements
necessary to update pg_proc so a drop/recreate wouldn't be necessary.
--
Michael Fuhr
http://www.fuhr.org/~mfuhr/
---(end of broadcast)---
TIP 6: Have
the new code with old
catalog entries that aren't STRICT (e.g., restored from a dump).
Should we leave the PG_ARGISNULL() checks in place as a safety
measure, or should the 8.1 Release Notes make it clear that the
functions need to be recreated (or pg_proc updated)?
--
Michael Fuhr
http
? Or is this more likely a problem
with OpenSSL?
regression.diffs attached.
--
Michael Fuhr
http://www.fuhr.org/~mfuhr/
*** ./expected/3des.out Sun Mar 20 22:24:51 2005
--- ./results/3des.out Tue Jul 5 08:20:26 2005
***
*** 17,23
select encode(encrypt('', 'foo', '3des'), 'hex
/sparc, OpenSSL 0.9.8-beta6, and HEAD.
I expect you'll need to submit the patch to pgsql-patches so it'll
get put in the queue.
Thanks.
--
Michael Fuhr
http://www.fuhr.org/~mfuhr/
---(end of broadcast)---
TIP 5: Have you checked our extensive FAQ
specific
cases that used to work. Anyone want to dig into the details?
It fails for any system column -- weren't there some changes recently
in how system columns are handled?
--
Michael Fuhr
http://www.fuhr.org/~mfuhr/
---(end of broadcast
On Tue, Jul 05, 2005 at 09:22:37PM -0600, Michael Fuhr wrote:
It fails for any system column -- weren't there some changes recently
in how system columns are handled?
...or was that just discussion that never resulted in any changes?
I'm still digging through the archives trying to find what
ran is from a different
build?
--
Michael Fuhr
http://www.fuhr.org/~mfuhr/
---(end of broadcast)---
TIP 5: Have you checked our extensive FAQ?
http://www.postgresql.org/docs/faq
...
Hmmm...in 0.9.8 the signature is back to what it was in 0.9.7[a-d]:
void DES_ecb3_encrypt(const_DES_cblock *input, DES_cblock *output,
DES_key_schedule *ks1,DES_key_schedule *ks2,
DES_key_schedule *ks3, int enc);
--
Michael Fuhr
http://www.fuhr.org
?
Sounds like a question for the OpenSSL developers. If a search
through their list archives or CVS repository doesn't yield the
answer, then maybe asking the question on one of their lists will.
--
Michael Fuhr
http://www.fuhr.org/~mfuhr/
---(end of broadcast
) at
execQual.c:3607
--
Michael Fuhr
http://www.fuhr.org/~mfuhr/
---(end of broadcast)---
TIP 5: don't forget to increase your free space map settings
of the last member of the list).
Yeah, I knew that returning a list was contrary to what was expected, but
I wanted to see what would happen. I wasn't expecting a core dump :-(
Thanks for the patch.
--
Michael Fuhr
http://www.fuhr.org/~mfuhr/
---(end of broadcast
) at common.c:501
This regression failure began after the recent Fix libpq memory
leak during PQreset() commit:
http://archives.postgresql.org/pgsql-committers/2005-07/msg00285.php
I just commented out the change and the regression tests now pass.
--
Michael Fuhr
http://www.fuhr.org/~mfuhr
if you installed a new
Python but not a new version of libpython.*.so, then plpython.so
might be linked against an old version.
Does this machine have ldd or the equivalent? If so, can you compare
ldd /path/to/python and ldd /path/to/plpython.so?
--
Michael Fuhr
http://www.fuhr.org/~mfuhr
On Tue, Jul 19, 2005 at 03:11:35PM -0500, Jim C. Nasby wrote:
On Tue, Jul 19, 2005 at 01:54:00PM -0600, Michael Fuhr wrote:
Does this machine have ldd or the equivalent? If so, can you compare
ldd /path/to/python and ldd /path/to/plpython.so?
Oddly, no, it doesn't seem to have ldd
-aliasing -g -bundle plpython.o
-L../../../src/port -L/opt/local/lib -bundle_loader
../../../src/backend/postgres -framework Python -o libplpython.0.0.so
Hmmm...what's that -framework Python business? Looks mighty
suspicious in light of the otool output.
--
Michael Fuhr
http://www.fuhr.org
On Thu, Jul 21, 2005 at 02:38:51PM +1000, Jamie Deppeler wrote:
I am doing it right
/usr/local/pgsql/bin/initdb -D /usr/local/pgsql/data
How are you determining that no user is being created? What are
you doing and what's the exact error message?
--
Michael Fuhr
http://www.fuhr.org/~mfuhr
them in a PL/pgSQL function that traps the
errors), or should we just leave the tests alone now that we think
we understand what's happening?
--
Michael Fuhr
http://www.fuhr.org/~mfuhr/
---(end of broadcast)---
TIP 4: Have you searched our list
is that it assumes a version of Python
based on the OS, which might clean up the current buildfarm but
that isn't really correct. Is there a better way to handle this?
--
Michael Fuhr
http://www.fuhr.org/~mfuhr/
plpython_error/.*-darwin=plpython_error_py23
-- test error handling, i forgot
it, say, plpython_error_1.out. Job done, and no OS dependence.
Thanks -- I overlooked that in src/test/regress/README.
--
Michael Fuhr
http://www.fuhr.org/~mfuhr/
---(end of broadcast)---
TIP 2: Don't 'kill -9' the postmaster
of functions
Schema | Name | Result data type | Argument data types
+--+--+-
pg_catalog | md5 | text | bytea
pg_catalog | md5 | text | text
(2 rows)
--
Michael Fuhr
http://www.fuhr.org/~mfuhr
a WITH_THREADS option that I don't think is
enabled by default. The Python port's Makefile, however, has a
WITHOUT_THREADS option, so I think it *does* build a threaded Python
by default.
--
Michael Fuhr
http://www.fuhr.org/~mfuhr/
---(end of broadcast)---
TIP
pthread_attr_setstacksize
U pthread_create
U pthread_detach
U pthread_self
% nm -D /usr/local/lib/perl5/5.8.7/mach/CORE/libperl.so | grep pthread
[no output]
--
Michael Fuhr
http://www.fuhr.org/~mfuhr/
---(end of broadcast
until you replace it (or
drop and recreate it), after which you get NULL. If you exit the
session and reconnect then it works again. I checked 8.0.3 and it
doesn't have this problem.
--
Michael Fuhr
http://www.fuhr.org/~mfuhr/
---(end of broadcast
;
$$ LANGUAGE plpgsql VOLATILE;
SELECT oidtest();
oidtest
-
(1 row)
\c test2
You are now connected to database test2.
SELECT oidtest();
oidtest
-
16568
(1 row)
--
Michael Fuhr
http://www.fuhr.org/~mfuhr/
---(end of broadcast
I've only seen the problem with PL/pgSQL's GET DIAGNOSTICS --
I haven't been able to reproduce it with PL/Tcl's spi_lastoid.
Is anybody with a deeper understanding of the code looking at this?
--
Michael Fuhr
http://www.fuhr.org/~mfuhr/
---(end of broadcast
On Wed, Jul 27, 2005 at 12:08:18AM -0400, Tom Lane wrote:
Michael Fuhr [EMAIL PROTECTED] writes:
Is anybody with a deeper understanding of the code looking at this?
I tried to reproduce the problem ... no joy ...
Hmmm...not even with the example that starts from initdb? I'm up
to date
On Wed, Jul 27, 2005 at 12:56:15AM -0400, Tom Lane wrote:
Michael Fuhr [EMAIL PROTECTED] writes:
Could this be platform-specific?
Seems that way. I tried it on HPUX 10.20/HPPA/gcc 2.95.3.
No luck on FreeBSD 4.11-STABLE/i386/gcc 2.95.4. The box that does
have a problem is Solaris 9/sparc
the initdb started one to work the first time
around.
Odd -- that one works (or rather, fails) every time for me on Solaris 9/
sparc/gcc 3.4.2.
--
Michael Fuhr
http://www.fuhr.org/~mfuhr/
---(end of broadcast)---
TIP 1: if posting/reading through
and psql having lastoid working at
all eliminates that part of the equation).
So far the problem does seem to be specific to whatever PL/pgSQL's
is doing, and it affects ROW_COUNT as well as RESULT_OID. I haven't
been able to reproduce the problem with PL/Tcl or with C and SPI.
--
Michael Fuhr
http
the variations in
behavior were due to different platforms having different garbage
on the stack.
--
Michael Fuhr
http://www.fuhr.org/~mfuhr/
---(end of broadcast)---
TIP 6: explain analyze is your friend
behavior?
sql_implementation_info is a table rather than a view, so its
contents are hardcoded by initdb. Would it make sense to turn it
into a view? This is admittedly a minor issue that might not merit
the effort, but it still seems wrong.
--
Michael Fuhr
http://www.fuhr.org/~mfuhr
ecpgerrno.h
#include sqlca.h
/* End of automatic include section */
#line 1 foo.pgc
int
main(void)
{
putchar(E'\n');
return 0;
}
--
Michael Fuhr
http://www.fuhr.org/~mfuhr/
---(end of broadcast)---
TIP 6: explain analyze is your friend
' in line 11.
sql error 'table nosuch_2 does not exist' in line 13.
A sniff of this connection shows both the SAVEPOINT and ROLLBACK TO
being executed and succeeding.
--
Michael Fuhr
http://www.fuhr.org/~mfuhr/
---(end of broadcast)---
TIP 6: explain
like implicit declaration of function `inv_getsize'.
That's a hint that something's wrong.
--
Michael Fuhr
---(end of broadcast)---
TIP 2: Don't 'kill -9' the postmaster
? The comment mentions that the list should
match USERSET and possibly SUSET, but I'm thinking it would be
useful to include everything SHOWable. In any case, a few USERSET
variables like check_function_bodies and escape_string_warning are
missing, so I'd like to add at least those.
--
Michael Fuhr
On Sat, Aug 13, 2005 at 10:33:55AM -0400, Tom Lane wrote:
Michael Fuhr [EMAIL PROTECTED] writes:
I count about 65 variables that SHOW shows that are missing from
pgsql_variables in tab-complete.c. Does the list intentionally
omit certain variables?
It's intentional that the tab
On Sat, Aug 13, 2005 at 09:25:34AM -0600, Michael Fuhr wrote:
Here's the list I came up with -- variables that SHOW shows that
aren't in psql's completion list.
Here's the list broken down by context:
PGC_USERSET
autocommit
check_function_bodies
debug_assertions
escape_string_warning
pg_settings;
count
---
161
(1 row)
--
Michael Fuhr
---(end of broadcast)---
TIP 9: In versions below 8.0, the planner will ignore your desire to
choose an index scan if your joining column's datatypes do not
match
On Sat, Aug 13, 2005 at 12:41:51PM -0400, Tom Lane wrote:
Michael Fuhr [EMAIL PROTECTED] writes:
Is 162 a typo or are you working on something that hasn't been
committed yet? I see 161 in the latest code.
Uh, I get 162 ... and no I don't have any uncommitted changes ATM.
I found
On Sat, Aug 13, 2005 at 11:04:18AM -0600, Michael Fuhr wrote:
I had removed --enable-cassert from my configure script while doing
some performance tests and never put it back (I had noticed that
VACUUM was quite slow on that box and found that it was due to the
assertion checks).
BTW, here
On Mon, Aug 15, 2005 at 10:37:06PM +, Matt Miller wrote:
Perhaps we should look at Expect or something similar.
Where can I get more info on Expect?
http://www.google.com/
:-)
Or here:
http://expect.nist.gov/
--
Michael Fuhr
---(end of broadcast
)
--
Michael Fuhr
---(end of broadcast)---
TIP 2: Don't 'kill -9' the postmaster
be rolled back without
affecting the outer transaction.
--
Michael Fuhr
---(end of broadcast)---
TIP 4: Have you searched our list archives?
http://archives.postgresql.org
(), is there any reason not to expose
it? I'd propose both sleep() and usleep() functions.
--
Michael Fuhr
---(end of broadcast)---
TIP 9: In versions below 8.0, the planner will ignore your desire to
choose an index scan if your joining column's
On Sun, Aug 21, 2005 at 09:13:20PM -0400, Tom Lane wrote:
Michael Fuhr [EMAIL PROTECTED] writes:
What do people think of exposing pg_usleep() to the user?
I'm not real enthused about it. Generally speaking, a sleep() on the
database side means you are idling while holding locks
. Is there a reason for
the inconsistency or is it just an oversight?
--
Michael Fuhr
---(end of broadcast)---
TIP 3: Have you checked our extensive FAQ?
http://www.postgresql.org/docs/faq
On Wed, Aug 24, 2005 at 12:49:57PM -0400, Bruce Momjian wrote:
Added to TODO:
o Add sleep() to PL/PgSQL
Just to PL/pgSQL? If we're going to add it (which doesn't seem to
be decided yet), why not as an ordinary function that could be
called from SQL as well?
--
Michael Fuhr
| foo
public | foo_val_idx | index | test | foo
(2 rows)
--
Michael Fuhr
---(end of broadcast)---
TIP 2: Don't 'kill -9' the postmaster
Aggregate (cost=38.53..38.53 rows=1 width=0)
- Seq Scan on foo (cost=0.00..36.75 rows=713 width=0)
Filter: (x 10)
(3 rows)
--
Michael Fuhr
---(end of broadcast)---
TIP 6: explain analyze
: (x 10)
(3 rows)
--
Michael Fuhr
---(end of broadcast)---
TIP 2: Don't 'kill -9' the postmaster
\b, isDone=0x0)
at execQual.c:2808
#2 0x0011f75c in ExecIndexEvalRuntimeKeys (econtext=0x4154f0,
run_keys=0x415588, scan_keys=0xffbfe34f, n_keys=0)
at nodeIndexscan.c:270
--
Michael Fuhr
---(end of broadcast)---
TIP 2: Don't 'kill -9
of PostgreSQL itself. Please post to one of the other
lists; if you're not sure which one then pgsql-general is usually
a good place.
--
Michael Fuhr
---(end of broadcast)---
TIP 4: Have you searched our list archives?
http
bla sdf yada yada s df sd fsd E...
^
From what I read in the release notes I was expecting to see this
raised at create time.
Create-time checking works here.
--
Michael Fuhr
---(end of broadcast)---
TIP 1: if posting/reading through
.
Tom (or anybody else), are there any gotchas with updating pg_language
like this? It works for me in simple tests.
--
Michael Fuhr
---(end of broadcast)---
TIP 4: Have you searched our list archives?
http://archives.postgresql.org
function was never
created. Try adding this before the UPDATE (stolen from pg_dump):
CREATE FUNCTION pg_catalog.plpgsql_validator(oid) RETURNS void
AS '$libdir/plpgsql', 'plpgsql_validator'
LANGUAGE c;
--
Michael Fuhr
---(end of broadcast)---
TIP 4: Have
- to connect to the
same database as a different user.
test= \c - postgres
You are now connected as new user postgres.
test=#
--
Michael Fuhr
---(end of broadcast)---
TIP 3: Have you checked our extensive FAQ?
http://www.postgresql.org/docs
On Tue, Sep 06, 2005 at 11:52:18PM +0400, Oleg Bartunov wrote:
btw, GiST programming tutorial is available in Russian,
http://www.sai.msu.su/~megera/postgres/talks/gist_tutorial.html
Cool. Is an English version in the works?
--
Michael Fuhr
---(end of broadcast
On Wed, Sep 07, 2005 at 03:51:05PM +0400, Teodor Sigaev wrote:
ERROR: relation with OID 16628 does not exist
CONTEXT: SQL statement SELECT count(*) from foo where bar = $1
http://www.postgresql.org/docs/faqs.FAQ.html#4.19
--
Michael Fuhr
---(end of broadcast
;
Where do the database server's logs go? You might be seeing duplicate
output because the server's logs are sent to the same terminal as the
client's output.
BTW, this doesn't belong on pgsql-hackers.
--
Michael Fuhr
---(end of broadcast)---
TIP
/src/test/regress/./tmp_check/data/base/1
... FATAL: shmat(id=8326) failed: Not enough space
--
Michael Fuhr
---(end of broadcast)---
TIP 6: explain analyze is your friend
On Fri, Sep 16, 2005 at 09:28:39AM -0600, Michael Fuhr wrote:
FWIW, I have a Solaris 9/sparc box with gcc 3.4.2 (same setup as
gerbil) and have no problems with REL7_2_STABLE through HEAD. I'll
test REL8_0_STABLE with gerbil's configure options when I get a
chance.
I just built REL8_0_STABLE
for differences between gerbil and my box
--
Michael Fuhr
---(end of broadcast)---
TIP 1: if posting/reading through Usenet, please send an appropriate
subscribe-nomail command to [EMAIL PROTECTED] so that your
message can get through
be overwritten. Does anybody else think
pg_dump shouldn't emit COMMENT ON DATABASE in these cases?
--
Michael Fuhr
---(end of broadcast)---
TIP 2: Don't 'kill -9' the postmaster
On Fri, Sep 23, 2005 at 04:45:02PM -0400, Bruce Momjian wrote:
Tom Lane wrote:
Michael Fuhr [EMAIL PROTECTED] writes:
Regarding the removal of ALTER INDEX OWNER commands from pg_dump,
indexes are now restored with the wrong ownership if the user doing
the restore is different than
that's actually true.
What if the query itself resulted in the disconnect by causing the
backend to crash? Re-running such a query automatically would be
a bad idea. Or did I misunderstand what you're asking?
--
Michael Fuhr
---(end of broadcast
Gerbil's looking better lately:
http://pgbuildfarm.org/cgi-bin/show_history.pl?nm=gerbilbr=REL8_0_STABLE
--
Michael Fuhr
---(end of broadcast)---
TIP 2: Don't 'kill -9' the postmaster
');
ERROR: could not open relation with OID 26237
test= SELECT pg_total_relation_size(26235);
ERROR: could not open relation with OID 26237
test= SELECT pg_relation_size('foo');
pg_relation_size
--
0
(1 row)
--
Michael Fuhr
---(end
strndup() in the Open Group Base Specifications, so I
expect other platforms' builds might fail as well.
--
Michael Fuhr
---(end of broadcast)---
TIP 4: Have you searched our list archives?
http://archives.postgresql.org
loops=1)
Index Cond: (abs(x) = 18)
Total runtime: 2.418 ms
(5 rows)
--
Michael Fuhr
---(end of broadcast)---
TIP 2: Don't 'kill -9' the postmaster
in better statistics for
expression index queries.
That difference in behavior seems odd: if default_statistics_target
has an effect, why doesn't ALTER TABLE SET STATISTICS?
--
Michael Fuhr
---(end of broadcast)---
TIP 1: if posting/reading through
those statistics were being stored, since they were affected by
default_statistics_target but not by per-column statistics targets.
And now I see them when I don't restrict queries against pg_stats
by just the table or column name. Thanks.
--
Michael Fuhr
---(end
://archives.postgresql.org/pgsql-hackers/2004-03/msg00502.php
No responses :-(
Would an ALTER INDEX SET STATISTICS form be possible?
--
Michael Fuhr
---(end of broadcast)---
TIP 4: Have you searched our list archives?
http://archives.postgresql.org
On Sat, Oct 01, 2005 at 02:42:32AM -0400, Tom Lane wrote:
Michael Fuhr [EMAIL PROTECTED] writes:
Would an ALTER INDEX SET STATISTICS form be possible?
It's not so much the table/index misnomer that's bothering me, it's
the lack of a clean way to identify which column of the index you
to be
emitting still another spelling of the encoding error message :-(
$ python -V
Python 2.2.3
The attached variant file (plpython_error_2.out) should allow this
Python version's wording of the error message.
--
Michael Fuhr
-- test error handling, i forgot to restore Warn_restart
is the latest).
http://archives.postgresql.org/pgsql-bugs/2005-04/msg00058.php
http://archives.postgresql.org/pgsql-committers/2005-04/msg00134.php
--
Michael Fuhr
---(end of broadcast)---
TIP 9: In versions below 8.0, the planner will ignore your
On Tue, Oct 18, 2005 at 09:41:21PM -0500, Larry Rosenman wrote:
I could not find a truss/strace binary on the box :(
In BSD land try ktrace.
--
Michael Fuhr
---(end of broadcast)---
TIP 6: explain analyze is your friend
?
--
Michael Fuhr
---(end of broadcast)---
TIP 3: Have you checked our extensive FAQ?
http://www.postgresql.org/docs/faq
may re-post your question in this list. You must try elsewhere
first!
You could use contrib/dblink, but perhaps you should be using schemas
instead of separate databases.
--
Michael Fuhr
---(end of broadcast)---
TIP 9: In versions below 8.0
1 - 100 of 291 matches
Mail list logo
