On Thu, Feb 10, 2011 at 12:03:49AM -0500, Tom Lane wrote:
strk s...@keybit.net writes:
I've finally completed the debugging phase and have
a minimal self-contained testcase showing the problem.
It has to do with INITIALLY DEFERRED constraints.
I looked into this and find that the issue
of the DROP SCHEMA CASCADE being executed, till
the ERROR comes out (lots of traces for cascading objects).
This is :
PostgreSQL 8.4.3 on x86_64-pc-linux-gnu, compiled by GCC gcc-4.4.real (Ubuntu
4.4.3-4ubuntu5) 4.4.3, 64-bit
Do you have an idea on how to further debug this ?
TIA.
--strk
I've handled to produce a small testcase:
http://strk.keybit.net/tmp/could_not_open_relation.sql
It still requires postgis (svn), but if anyone has that it might help.
Will try to go on with the reduction.
--strk;
On Mon, Feb 07, 2011 at 12:38:08PM +0100, strk wrote:
Hi all,
I'm trying
)
DEFERRABLE
INITIALLY DEFERRED
--strk;
() Free GIS Flash consultant/developer
/\ http://strk.keybit.net/services.html
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
On Mon, Feb 07, 2011 at 02:31:49PM +0100, Dimitri Fontaine wrote:
strk s...@keybit.net writes:
Do you have an idea on how to further debug this ?
That usually goes with providing a self-contained test case⦠that is a
minimum script that creates the function(s) and calls them.
I've
doesn't
quite address. Putting hstore in would let all the other PLs use it,
to the extent that they need such a thing. :)
Plus pure SQL use !
I was considering using hstore for a table value too for
a form of historic table. Just to say I'd also be happy with
it being core in pgsql :)
--strk
On Wed, Mar 10, 2010 at 07:50:16AM -0500, Andrew Dunstan wrote:
Using an hstore in 9.0 it's not too bad,
Does it still have a limit of 65535 bytes per field ?
--strk;
() Free GIS Flash consultant/developer
/\ http://strk.keybit.net/services.html
--
Sent via pgsql-hackers mailing
How can a pl/pgsql trigger change the
values of dynamic fields in NEW record ?
By dynamic I mean that the field name
is a variable in the trigger context.
I've been told it's easy to do with pl/perl but
I'd like to delive a pl/pgsql solution to have
less dependencies.
Thanks in advance.
--strk
On Tue, Mar 09, 2010 at 06:59:31PM +0100, Pavel Stehule wrote:
2010/3/9 strk s...@keybit.net:
How can a pl/pgsql trigger change the
values of dynamic fields in NEW record ?
By dynamic I mean that the field name
is a variable in the trigger context.
I've been told it's easy to do
pg_advisory_lock(q.id) FROM
(
SELECT id FROM foo WHERE id 12345 LIMIT 100;
) q; -- ok
Last statement seems bogus to me ...
--strk;
() Free GIS Flash consultant/developer
/\ http://foo.keybit.net/~strk/services.html
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make
build works fine
(no -Bforcearchive flag used)
If I remove the -Bforcearchive flag from Makefile.shlib
everything seems to work fine.
I suppose (but didn't test) that this would also fail with
pgxs. Are there freebsd users around to test this ?
--strk;
---(end of broadcast
, and the link switches
are different then.
Thank you, it's ELF_SYSTEM undefined.
We just copied Makefile.shlib, not Makefile.global.
We'll have to add a check for ELF_SYSTEM in our own configure script.
Wouldn't this be a problem for pgxs-compiled modules as well ?
--strk
'';
return ''ret''::text;
END ' LANGUAGE 'plpgsql' IMMUTABLE STRICT;
PostgreSQL version 8.0.0
--strk;
---(end of broadcast)---
TIP 4: Have you searched our list archives?
http://archives.postgresql.org
is memory hold ?
Is there an index-specific memory context for use
to early release memory blocks allocated during
operations (didn't see any use of memory contexts
in the contrib/rtree_gist) ?
TIA
--strk;
---(end of broadcast)---
TIP 1
Missing info for the report:
win32
postgresql 8.0.3
maintenance_work_mem 512
btree index on oid works fine
--strk;
On Sat, Aug 13, 2005 at 01:12:30PM +0200, [EMAIL PROTECTED] wrote:
Hi all.
I've been reported memory limit hits
during a postgis index
On Tue, Jun 28, 2005 at 08:12:16PM -0400, Bruce Momjian wrote:
strk wrote:
The valure returned from pg_config --includedir-server
is broken as of CVS.
It points to unexistent directory:
/home/extra/pgroot-cvs/include/server
Correct value would be:
/home/extra/pgroot-cvs/include
The valure returned from pg_config --includedir-server
is broken as of CVS.
It points to unexistent directory:
/home/extra/pgroot-cvs/include/server
Correct value would be:
/home/extra/pgroot-cvs/include/postgresql/server
--strk;
---(end of broadcast
Is it possible to access postgres configuration from
a C stored procedure ?
I need to leverage memory usage and I'd use postgres configuration
rather then a compile-time define.
Is there such a configuration, if access is possible ?
--strk;
---(end of broadcast
On Mon, Jun 27, 2005 at 08:55:50AM -0400, Dave Cramer wrote:
you can use show xxx to show configuration values
http://www.postgresql.org/docs/7.4/interactive/sql-show.html
No direct interface for shared libs ?
--strk;
---(end of broadcast
(restart/vacuum full don't help)
ERROR: cache lookup failed for relation 1250714
Any hint?
--strk;
---(end of broadcast)---
TIP 7: don't forget to increase your free space map settings
On Wed, Mar 23, 2005 at 01:48:11PM +, Richard Huxton wrote:
strk wrote:
Hello.
A memory fault in a trigger left my database
in a corrupted state:
- I can't create temporary tables anymore
(restart/vacuum full don't help)
ERROR: cache lookup failed for relation
On Wed, Mar 23, 2005 at 02:49:53PM +, Richard Huxton wrote:
strk wrote:
On Wed, Mar 23, 2005 at 01:48:11PM +, Richard Huxton wrote:
strk wrote:
Hello.
A memory fault in a trigger left my database
in a corrupted state:
- I can't create temporary tables anymore
It is embarassing for me, but I could not reproduce the bug. :(
Maybe I just ended up with a corrupted database (or I was just too tired).
Behaviour seems to be the same for both SQL and pl/pgsql functions on
a new database (and I got rid of the old one).
Sorry.
--strk;
On Thu, Mar 17, 2005
= $1;
END
' LANGUAGE 'plpgsql' IMMUTABLE STRICT;
Is this expected ?
--strk;
---(end of broadcast)---
TIP 6: Have you searched our list archives?
http://archives.postgresql.org
I've tested with 8.0.1 and get same results.
--strk;
On Wed, Mar 16, 2005 at 01:04:03PM +0100, [EMAIL PROTECTED] wrote:
On postgresql-8.0.0 I've faced a *really* weird behavior.
A simple query (single table - simple function call - no index),
makes postgres process grow about as much
I've tried with 7.4.3 - *good* results with both SQL and PL/PGSQL
(actually even less that best 8.0.1: 12Mb)
I think this makes it a bug...
--strk;
On Wed, Mar 16, 2005 at 01:58:44PM +0100, [EMAIL PROTECTED] wrote:
I've tested with 8.0.1 and get same results.
--strk;
On Wed, Mar 16
output within a single query, isn't the shown one
a single query ?
Thanks in advance
--strk;
-- VOLATILE
update pg_proc set provolatile = 'v' where proname = 'find_srid';
UPDATE 1
explain analyze select * from input.geobit_5 where the_geom
setsrid('BOX3D(.7e+06 4.6e+06, .8e+06 4.83e+06)'::box3d
:
- obtain OID of a given argument
- obtain OID of a given type by its name
By easy I mean not involving a query to the backend.
--strk;
For standing up against patentability of software,
Thank You, Poland!
Read the intervention:http://kwiki.ffii.org/ConsPolon041221En
Send your thanks
as Version 1 ?
TIA
--strk;
For standing up against patentability of software,
Thank You, Poland!
Read the intervention:http://kwiki.ffii.org/ConsPolon041221En
Send your thanks: thankyoupoland.info
Read/do more: http://www.noepatents.org/
---(end
Sorry, my fault, just mistyped the function name
in PG_FUNCTION_INFO_V1() macro.
--strk;
On Wed, Dec 29, 2004 at 11:08:28AM +0100, strk wrote:
I'm trying to implement a trigger within 8.0.0RC2.
I get a segfault when the trigger is fired, valgrind
reports an illegal read being the line
32 rows
a full join makes the estimate=1088 rows ( 34*32 )
a join with a filter on test2 makes estimate=34 ( 34*1 ? )
strk=# explain analyze select * from test1, test2 where test1.geom
test2.geom;
NOTICE: LWGEOM_gist_joinsel called (returning 1.00
it should NOT depend on full number of rows either, is this right ?
--strk;
regards, tom lane
---(end of broadcast)---
TIP 6: Have you searched our list archives?
http://archives.postgresql.org
access to RESTRICTSEL output for REL1 and REL2 ?
--strk;
---(end of broadcast)---
TIP 7: don't forget to increase your free space map settings
for a long time:
2002-10-12 00:52 dblasby
* postgis_estimate.c: New file with original estimation methods.
--strk;
--
greg
---(end of broadcast)---
TIP 2: you can get off all lists at once with the unregister command
(send
On Mon, Dec 13, 2004 at 03:04:01PM -, Mark Cave-Ayland wrote:
Hi strk,
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
Sent: 13 December 2004 14:05
To: Mark Cave-Ayland
Cc: [EMAIL PROTECTED]
Subject: Re: [postgis-devel] RE: join selectivity
TIA
--strk;
---(end of broadcast)---
TIP 8: explain analyze is your friend
testing in a context where both tables have indexes that are
relevant to the operator?
Single index relevant to the operator makes 2 calls to RESTRICT.
Double index (one for each table) makes 4 calls to RESTRICT.
In both cases JOIN is called once.
--strk;
The estimated join result size
Current pg_restore segfaults.
Manually fault seems to happen at (*AH-ClosePtr) (AH)
in pg_backup_archiver.c/CloseArchive(Archive *)
--strk;
---(end of broadcast)---
TIP 5: Have you checked our extensive FAQ?
http
width=81)
(actual time=0.39..19.22 rows=75 loop=1)
Total runtime: 19.37 msecs
--strk;
---(end of broadcast)---
TIP 3: if posting/reading through Usenet, please send an appropriate
subscribe-nomail command to [EMAIL PROTECTED] so
On Tue, Sep 14, 2004 at 10:45:16PM +1000, Philip Warner wrote:
At 06:55 PM 14/09/2004, strk wrote:
Current pg_restore segfaults.
You might need to give a little more information; does it only segfault for
a specific DB? Does it segfault for a trivial empty DB? Can you construct a
minimal
On Tue, Sep 14, 2004 at 10:55:46AM -0400, Tom Lane wrote:
strk [EMAIL PROTECTED] writes:
Trying to make minimal example I found out it's pg_dump too.
Example:
$ pg_dump template1
...
Segmentation Fault
You've got a broken build then, or a platform-specific problem.
Check
On Mon, Aug 23, 2004 at 03:20:09PM -0400, Tom Lane wrote:
strk [EMAIL PROTECTED] writes:
Is returning a pointer to the input safe in every case ?
You mean for returning *unmodified* input, don't you?
Yes, that's safe. Scribbling on input values is definitely never safe
Is returning a pointer to the input safe in every case ?
--strk;
---(end of broadcast)---
TIP 1: subscribe and unsubscribe commands go to [EMAIL PROTECTED]
encoded somehow ?
TIA
--strk;
---(end of broadcast)---
TIP 6: Have you searched our list archives?
http://archives.postgresql.org
On Fri, Aug 13, 2004 at 08:42:44PM +1000, Philip Warner wrote:
At 08:09 PM 13/08/2004, strk wrote:
What does 'Dump Version' refer to then ? Are these ToC output
changes encoded somehow ?
The file format version of pg_dump; the actual contents depend on pg_dump
version, and the source
in the form:
From PG73:
552; 2663984 CAST bytea (public.wkb)
From PG74:
547; 1915318 CAST CAST (public.wkb AS bytea)
Since these two dumps have same file format version I asked..
--strk;
On Fri, Aug 13, 2004 at 10:05:09PM +1000, Philip Warner wrote:
At 08:53 PM 13/08/2004, strk wrote
On Fri, Aug 13, 2004 at 11:12:50PM +1000, Philip Warner wrote:
At 10:30 PM 13/08/2004, strk wrote:
From PG73:
552; 2663984 CAST bytea (public.wkb)
From PG74:
547; 1915318 CAST CAST (public.wkb AS bytea)
Since these two dumps have same file format version I asked
,
nor it is at vacuum time.
A currupted catalog set is probably be the reason.
Shouldn't pg_dump warn about that ?
Is there a catalog corruption detection app ?
TIA
--strk;
On Sun, Aug 08, 2004 at 01:40:40PM +0200, strk wrote:
On Sun, Aug 08, 2004 at 12:50:43PM +0800, Christopher Kings-Lynne
.
That someone is probably me, but I don't remember pg_dump
giving me any warning about this. Also I think I've run vacuum
on the db before dumping.
As before I'm not on the source computer so I can't send the
pg_dump -s, but if you want, I can send you the pg_restore -l.
--strk;
Chris
reason I can imagine for this is pg_dump taking
any sequence whose name ends in _seq as being associated
to a table, no matter if that table exists and has a 'serial'
field. Is this possible ? Shouldn't this kind of dependency
be coded somehow ?
TIA
--strk;
---(end
with what was probably it's oid instead.
Is this a bug in pg_dump ?
How do I tell which pg_dump version produced the dump ?
Is self commutation valid ?
TIA
--strk;
---(end of broadcast)---
TIP 7: don't forget to increase your free space map settings
?
--
-- TOC entry 537 (OID 2663955)
-- Name: ~=; Type: OPERATOR; Schema: public; Owner: strk
-- Data Pos: 0
--
CREATE OPERATOR ~= (
PROCEDURE = geometry_same,
LEFTARG = geometry,
RIGHTARG = geometry,
COMMUTATOR = 2663954,
RESTRICT = eqsel,
JOIN = eqjoinsel
);
Is this a bug
On Tue, Aug 03, 2004 at 05:17:27PM +0800, Christopher Kings-Lynne wrote:
--
-- TOC entry 537 (OID 2663955)
-- Name: ~=; Type: OPERATOR; Schema: public; Owner: strk
-- Data Pos: 0
--
CREATE OPERATOR ~= (
PROCEDURE = geometry_same,
LEFTARG = geometry,
RIGHTARG = geometry
(a); drop index test_idx;
create index test_idx on test (a); drop index test_idx;
...
The size growth is reported by 'top' in the fields
SIZE, RSS and SHARE.
The database is a newly created one after first initdb
as of CVS 20040311.
Can it be a memory leak in postgres code ?
TIA
--strk
Working with current CVS:
$ createlang plpgsql
createlang: language installation failed:
ERROR: could not load library /pgroot-cvs/lib/postgresql/plpgsql.so:
/pgroot-cvs/lib/postgresql/plpgsql.so:
undefined symbol: downcase_truncate_identifier
--strk;
---(end
Is there a quick way to use the BYTE_ORDER define
as set by pgsql ? I can't find an entry point
include for it.
It's needed for postgis (problems with Solaris BYTE_ORDER).
--strk;
---(end of broadcast)---
TIP 1: subscribe and unsubscribe commands
(parameter) can be the general postgres version.
while varchar(2) 'string' can be the standard SQL version (not general).
--strk;
Will this work: 'string'::typename
Yes, since the :: cues the parser to expect a typename next.
regards, tom lane
on pg_class.
Where is this sequence-to-relation association stored so that
i can clean it up ?
NOTE: vacuum full does not solve this.
TIA
-strk;
---(end of broadcast)---
TIP 1: subscribe and unsubscribe commands go to [EMAIL PROTECTED]
in
text-internal conversion and is showing heap corruption problems.
The question now is: what does that message mean ? Did a routine
try to create an index and left its work before finishing it ?
--strk;
JanWieck wrote:
Christopher Kings-Lynne wrote:
I couldn't agree more. Look
)
Do you have any hint about how to fix this ?
TIA
--strk;
---(end of broadcast)---
TIP 2: you can get off all lists at once with the unregister command
(send unregister YourEmailAddressHere to [EMAIL PROTECTED])
JanWieck wrote:
strk wrote:
I get the following error when vacuuming a db or inserting
a big value in a column of a toastable datatype (GEOMETRY).
ERROR: Index pg_toast_8443892_index is not a btree
My last action has been killing a psql that was getting
mad about receiving
tgl wrote:
strk [EMAIL PROTECTED] writes:
gis=# reindex table pg_toast_8443892; -- this was an assuption I made
ERROR: Relation pg_toast_8443892 does not exist
If it's 7.3 or later you need to say
reindex table pg_toast.pg_toast_8443892;
regards, tom lane
tgl wrote:
strk [EMAIL PROTECTED] writes:
Testing postgis support in PG7.4 (2003-11-11)
I've encountered to this problem:
ERROR: could not identify an ordering operator for type geometry
Previous PG versions does not show this problem.
Any hint on what might be missing
~ | geometry| geometry
= | geometry| geometry
| geometry| geometry
| geometry| geometry
(11 rows)
Previous PG versions does not show this problem.
Any hint on what might be missing ?
--strk;
---(end of broadcast
Running initdb:
creating template1 database in /pgroot-cvs/data/base/1 ... child process was
terminated by signal 11
---(end of broadcast)---
TIP 9: the planner will ignore your desire to choose an index scan if your
joining column's
is missing something
(make distclean made it work)
Thanks for you support
--strk;
---(end of broadcast)---
TIP 7: don't forget to increase your free space map settings
Does with(isStrict) still work ?
If not when did postgres drop its support ?
TIA
--strk;
---(end of broadcast)---
TIP 1: subscribe and unsubscribe commands go to [EMAIL PROTECTED]
I can't build postgresql from CVS. Any help ?
This is the message I get:
bison -y -d preproc.y
preproc.y:6275: fatal error: maximum table size (32767) exceeded
Bison version:
bison (GNU Bison) 1.35
TIA
.strk;
--
pallamondo.net -- take a look
is: if I write in the state array
pointers to DETOASTED input args,
will I find them intact at finalfunc time ?
TIA
--strk;
---(end of broadcast)---
TIP 4: Don't 'kill -9' the postmaster
the DETOASTed datum, I'd like to avoid one
copy.
TIA.
--strk;
---(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
with it ?
NOTE that if I MemoryContextAllocate in fcinfo-flinfo-fn_mcxt and
memcopy DETOASTED geom, everything works (ar at least it seems to)
--strk;
strk wrote:
Tom, thanks again for the quick answer and
sorry for the lame question about memor allocation.
I hope this is acceptable
tgl wrote:
strk [EMAIL PROTECTED] writes:
From whitin an aggregate sfunc I did:
oldcontext = MemoryContextSwitchTo(fcinfo-flinfo-fn_mcxt);
geom = (GEOMETRY *)PG_DETOAST_DATUM(datum);
MemoryContextSwitchTo(oldcontext);
And later in aggregate's finalfunc
? To note also that the same identical calls keeps
making SIZE grow ...
PS: I'm working with postgres-7.3.2
TIA
--strk;
---(end of broadcast)---
TIP 6: Have you searched our list archives?
http://archives.postgresql.org
73 matches
Mail list logo
