ct" the first result is an update count, not a
ResultSet. You need to move to the next result, which is actually a
ResultSet.
Kris Jurka
---(end of broadcast)---
TIP 6: Have you searched our list archives?
http://archives.postgresql.org
db) or not String (as they should be) - this fails.
Could we see an actual failure scenario (stacktrace) here? I don't see
why a large number of properties would be a problem. A non-String object
in a Properties is a problem in the calling code, not ours.
Kris Jurka
---
With the promised files this time.
On Sat, 23 Apr 2005, Kris Jurka wrote:
>
> The 8.1 server doesn't work when issuing queries using the v2 protocol,
> notably the isnull bitmask in the DataRow message is incorrect. I suspect
> the problem is with this
utput from establishing a connection with the
JDBC driver using the V2 protocol to a 7.4 and an 8.1 server. In the 7.4
server after the 'D' message is c0 while 8.1 has 00 as the next byte.
Kris Jurka
---(end of broadcast)---
TIP 8: explain analyze is your friend
On Fri, 22 Apr 2005, Oliver Jowett wrote:
> Ingolf Knopf wrote:
> > Bug reference: 1611
> > PostgreSQL version: 8.0.1
> > Operating system: JDBC
> > Description:reading a date-field by "ResultSet.getTimestamp()"
> > method analized dayligth flag
> > Details:
> >
> > Retrieving d
ed boolean unique set to false :
> - this value should apply to Non Unique Index
> - Non Unique Index have a returned boolean unique set to true :
> - this value should apply to Unique Index
>
If you check the javadoc for getIndexInfo you will see column four is
actually
of binary data, which it shouldn't. Are you
sure you are using version 7.3.9? Here I have 7.3.0, 7.3.1, 7.3.2, and
7.3.9. The only one that has that bug is 7.3.2. I don't know when this
was fixed, but I have no trouble with 7.3.9.
Kris Jurka
---(end of broadca
9-10
> 01:00:00.0")
> Maybe UTC time ? but suerly a bug...
>
There is a known bug in the 8.0 jdbc driver when the client and server are
in different timezones. Is that the case here?
Kris Jurka
---(end of broadcast)---
TIP 6: H
xisting implementation of ResultSetMetaData.getPrecision.
Kris Jurka
---(end of broadcast)---
TIP 5: Have you checked our extensive FAQ?
http://www.postgresql.org/docs/faq
On Sun, 6 Feb 2005, Tom Lane wrote:
> Kris Jurka <[EMAIL PROTECTED]> writes:
> > The documentation says the time with time zone datatype allows zone
> > offsets from +12 to -12.
>
> I see noplace that opines on this at all ...
>
http://www.postgresq
think it will be complicated on the error handling/cleanup side,
especially with a multithreaded application. You set it, you execute a
statement, and then you've got to reset it back to the default so other
threads aren't affected by it.
Kris Jurka
-
urka=# select '00:00:00'::timetz;
timetz
-
00:00:00+14
(1 row)
but this is not an allowed value:
jurka=# select '00:00:00+14'::timetz;
ERROR: time zone displacement out of range: "00:00:00+14"
Kris Jurka
---(end of
ReceiveInteger(int siz) throws SQLException
> {
This is not a bug. The ReceiveInteger function you are looking at is a
part of the low level protocol code and int size will never be > 4. It
has nothing to do with how something like ResultSet.getLong() treats
in
On Wed, 19 Jan 2005, jerome celle wrote:
> With following entry in pg_hba.conf :
> host all all 192.168.2.0/32 trust
>
> I get the following error when attempting to open a connection from
> 192.168.2.27 host :
Perhaps you want 192.168.2.0/24.
Kris Jurka
---
On Tue, 18 Jan 2005, Woung raxfar wrote:
> CREATE TABLE users
> (
> s_no varchar(6),
> userid varchar(20)
> )
I don't believe getPrecision is intended to operate on non-numeric fields.
Perhaps you are looking for getColumnDisplaySize() ?
Kris Jurka
--
ot to get Precision and Scale
>
What underlying data type are you trying to call these methods on? You
need to provide some more information to describe what you are doing.
Kris Jurka
---(end of broadcast)---
TIP 2: you can get off all lists at
d used the old
> pg74.214.jdbc3.jar and it worked!
>
> What logs can be useful to collect for deep investigation?
>
How about just starting with a brief description of the problem: what you
tried to do, what happened, and what you expected to happen. Simply
sa
. this reference directly
> stops the service from starting.
>
8.0 has replaced the tcpip_socket flag with the listen_addresses setting
which specifies which addresses to listen on.
Kris Jurka
---(end of broadcast)---
TIP 6: H
non-password based methods.
Kris Jurka
---(end of broadcast)---
TIP 7: don't forget to increase your free space map settings
I sent him a driver that was recompiled with MAX_BUFFERED_QUERIES = 1 and
he still appears to be having some problems, but I have no idea where.
Kris Jurka
-- Forwarded message --
Date: Mon, 13 Dec 2004 06:51:10 -0800 (PST)
From: Bahadur Singh <[EMAIL PROTECTED]>
To: Kris
ribed in the
below code comment. When originally written I asked Oliver about the
estimate of MAX_BUFFERED_QUERIES and he felt confident in that number. It
would be good to know if lowering this number fixes your problem.
Kris Jurka
// Deadlock avoidance:
//
// It's possi
tell if
the insert is a duplicate key error or is valid, so it must wait for
Session 1 to do something first. This is likely the "frozing mode" you
are seeing as the insert waits.
Kris Jurka
---(end of broadcast)---
TIP 5: H
so I reported it and Tom Lane fixed it:
http://archives.postgresql.org/pgsql-bugs/2004-11/msg00066.php
Kris Jurka
---(end of broadcast)---
TIP 2: you can get off all lists at once with the unregister command
(send "unregister YourEmail
ork OK in 7.4 (even though the
> supportsCatalogsInDataManipulation() returned false there also).
>
This did not work in 7.4 either, it even gives a much better error message
than 8.0's "syntax error"
jurka=# select * from catalog.schem.tab;
ERROR: cross-database refer
d to a = '0' before being sent to
the server. Now it uses a true prepared statement on the server side
which needs the correct types given to it.
Kris Jurka
---(end of broadcast)---
TIP 5: Have you checked our extensive FAQ?
read Exception in thread "Timer-1"
> java.lang.ClassCastException: java.lang.Short
> at
> org.postgresql.jdbc2.AbstractJdbc2Statement.getShort(AbstractJdbc2Statement.java:1681)
This has already been fixed in cvs.
Kris Jurka
---(end of broadcast)--
Creating a domain on bit(N) doesn't seem to work as expected when casting
to the domain type.
CREATE DOMAIN bit4 AS bit(4);
SELECT 7::bit(4), 7::bit4;
bit | bit4
--+--
0111 | 1000
(1 row)
Reported in #postgresql by msw_alt.
Kris Jurka
---(e
I'd like to re-raise this bug I reported some time ago and got no response
on. Generally any plain sql commands shouldn't crash the backend and I
don't like a query reporting incorrect results.
On Sun, 27 Jun 2004, Kris Jurka wrote:
> There are problems when a prepared stat
Compiling on solaris with a non gcc compiler does not correctly enable
debugging when --enable-debug is specified. src/template/solaris is
specifying CFLAGS="-O -v" and -O overrides the -g that --enable-debug
adds.
Kris Jurka
---(end of
PostgreSQL allows aggregates other than COUNT to accept * as the arugment.
Combined with the transformation of * -> 1 you get odd results from SELECT
MIN(*), MAX(*) FROM tab; instead of an error.
Kris Jurka
---(end of broadcast)---
TIP 2:
On Fri, 22 Oct 2004, Tom Lane wrote:
> You are confusing the syntax for a typed literal with part of the AT
> TIME ZONE construct.
Could you explain what the difference is between a typed literal
"int '11'" and a cast(ed) literal "'11'::int" to
r 57
These work:
PREPARE mys(interval) AS SELECT now() AT TIME ZONE $1;
PREPARE mys(text) AS SELECT now() AT TIME ZONE ($1::interval)
Any reason why the second case doesn't work?
Kris Jurka
---(end of broadcast)---
TIP 5: Have you checked our
for
some time now, so I'm worried about backwards compatibility.
Kris Jurka
---(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 Tue, 19 Oct 2004, federico wrote:
> i saw in bug 1201 that some got my problem
> [ you can't do "SELECT * FROM func_returning_void();" ]
This patch seems to fix it, although I have no idea what the actual
implications are, I just changed any place that produced an err
nctions that do not produce this error when called with a NULL argument.
jurka=# CREATE FUNCTION g(int) RETURNS int AS 'SELECT 1;' LANGUAGE sql;
CREATE FUNCTION
jurka=# CREATE FUNCTION g(float) RETURNS int AS 'SELECT 2;' LANGUAGE sql;
CREATE FUNCTION
jurka=# SELECT g(NUL
happened.
Kris Jurka
---(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
LException: SQLState(23505)
<=BE ReadyForQuery(E)
simple execute,
[EMAIL PROTECTED],
maxRows=0, fetchSize=0, flags=23
FE=> Parse(stmt=null,query="ROLLBACK TO SAVEPOINT
JDBC_SAVEPOINT_0",oids={})
FE=> Bind(stmt=null,portal=null)
FE=> Execute(portal=null,limit=1)
FE=> Sync
FE
93e43 in BackendStartup (port=0x834a210) at postmaster.c:2470
#13 0x0819209a in ServerLoop () at postmaster.c:1215
#14 0x081911ae in PostmasterMain (argc=3, argv=0x833add8) at
postmaster.c:898
#15 0x0815b655 in main (argc=3, argv=0x833add8) at main.c:265
Kris Jurka
---(end of broadcast)---
TIP 4: Don't 'kill -9' the postmaster
on: ERROR: column "showemail" is of type boolean but
> expression is of type text
Are you using something like PreparedStatement.setString to compose this
query? You should be using setBoolean instead I imagine.
Kris Jurka
---(end of broadcast)
tating that you are in a transaction. The
8.0 driver can be used against earlier servers if you'd like.
Kris Jurka
---(end of broadcast)---
TIP 7: don't forget to increase your free space map settings
> Bug reference: 1233
> Description:JDBC driver: moveToCurrentRow fails
>
Fixed in 7.4 and 8.0 branches. Thanks for the fix and sorry for the
delay, I've been travelling.
Kris Jurka
---(end of broadcast)---
TIP 4:
On Fri, 6 Aug 2004, Donald Fraser wrote:
> PostgreSQL version 7.4.3 JDBC Driver The notifcations for the version 3
> protocol are not being decoded at all in the jdbc driver.
>
> Here is the unix diff. which will correct this bug.
>
Fixed. Than
h argument to psql? By default psql does not
use tcpip to connect to the server.
Kris Jurka
---(end of broadcast)---
TIP 6: Have you searched our list archives?
http://archives.postgresql.org
tional build tool called ant
which is available from http://ant.apache.org/ If you do not want to
download and install this you can download a prebuilt jar file from
http://jdbc.postgresql.org/download.html
Kris Jurka
---(end of broadcast)---
TIP
On Thu, 29 Jul 2004, Kris Jurka wrote:
>
>
> On Thu, 29 Jul 2004, Tom Lane wrote:
>
> > There's no Assert at line 574 in CVS tip; how far back is your copy?
> > I think this might be related to some changes I made recently, so
> > please try if it still
ich did an rm -rf data ; initdb -D data from underneath a postmaster
that was in the process of shutting down.
Kris Jurka
---(end of broadcast)---
TIP 3: if posting/reading through Usenet, please send an appropriate
subscribe-nomail command to [EM
On Thu, 29 Jul 2004, Tom Lane wrote:
> This appears to be here:
>
> ereport(PANIC,
> (errcode_for_file_access(),
> errmsg("could not open control file \"%s\": %m",
> ControlFilePath)));
>
> but it's difficult to go any further wi
On Thu, 29 Jul 2004, Kris Jurka wrote:
>
> Running the JDBC driver's regression tests I came across an assertion
> failure in 7.5dev. The test does:
>
This also produces a second core file in the directory the postmaster was
started in which contains:
#0 0x402a5721 in
Running the JDBC driver's regression tests I came across an assertion
failure in 7.5dev. The test does:
BEGIN;
SELECT 1/0;
COMMIT;
and gets the following stacktrace. Note this cannot be replicated in psql
because it requires using the extended query protocol.
Kris Jurka
#0 0x402a57
select
'{{2001-01-01},{2001-02-02,2003-03-03},{2004-02-02,2004-04-04}}'::date[][];
date
---
{{2001-01-01,2000-01-01},{2001-02-02
ACE FUNCTION voidfunc() RETURNS void AS
'begin return; end;'
LANGUAGE plpgsql;
SELECT * FROM voidfunc();
ERROR: function "voidfunc" in FROM has unsupported return type
It is unclear why this is disallowed. A plain "SELECT voidfunc();" works.
Kris Jurka
-
matching
dimensions
Tested on both 7.4.3 and 7.5dev.
Kris Jurka
jurka=# SELECT '{{1,2},{2,3},{4}}'::int[][];
int4
---
{{1},{2},{4}}
jurka=# SELECT '{{1},{2,3},{4,5}}'::int[][];
int4
-
{{1,0},{2,3},{4,5}}
---
ows Bad
> BigDecimal Exception
>
> i'm working with NUMERIC(32,16) arrays in a DB table.
>
> nevertheless, JDBC retrieval causes a 'Bad BigDecimal Exception' beeing
> thrown for cases when there are non- integer values in the corresponding
> array.
>
Fixe
ATER VIEW v AS SELECT (a+b)::numeric(6,2) FROM tab;
Kris Jurka
---(end of broadcast)---
TIP 7: don't forget to increase your free space map settings
TO mytab VALUES (1);
PREPARE mystat AS SELECT a FROM mytab;
and then:
ALTER TABLE mytab ALTER COLUMN a TYPE bigint USING (a+1);
EXECUTE mystat;
or:
ALTER TABLE mytab ADD COLUMN b bigint;
UPDATE mytab SET b = a+1;
ALTER TABLE mytab DROP COLUMN a;
ALTER TABLE mytab RENAME COLUMN b TO a;
EXECUTE
Dumping and restoring the regression database in cvs tip gives the
following error upon restore:
ERROR: invalid input syntax for type timestamp with time zone:
"0097-02-16 17:32:01 BC-08"
CONTEXT: COPY timestamptz_tbl, line 42, column d1: "0097-02-16 17:32:01
BC-
onnection.java:352)
This bug was fixed in build 213 of the jdbc driver. Please download a
newer version from http://jdbc.postgresql.org/download.html
Kris Jurka
---(end of broadcast)---
TIP 1: subscribe and unsubscribe commands go to [EMAIL PROTECTED]
com/bugdatabase/view_bug.do?bug_id=4510956
they have no intention of making toString work for year values > .
I'll look at working around this on the driver side.
Kris Jurka
---(end of broadcast)---
TIP 3: if posting/reading throu
On Thu, 17 Jun 2004, Kris Jurka wrote:
>
>
> On Thu, 17 Jun 2004, PostgreSQL Bugs List wrote:
>
> >
> > The following bug has been logged online:
> >
> > Bug reference: 1168
> > PostgreSQL version: 7.4
> >
> > Descrip
On Thu, 17 Jun 2004, Werner Bohl wrote:
> On Thu, 2004-06-17 at 14:09, Kris Jurka wrote:
> > On Thu, 17 Jun 2004, PostgreSQL Bugs List wrote:
> >
> > > Postgresql version: 7.4.3
> > > Java: j2sdk_1.4.2_04
> > > ant: 1.5.2-26
> >
ngled, but I suspect you might have another
version of the driver somewhere on the classpath. The driver will fail
to compile in this situation as it gets confused with the
different versions of the same class.
Kris Jurka
---(end of broadcast)-
r me with the 1.5 JDK. Between 7.4.2 and 7.4.3 I did
make this change:
revision 1.36.2.2
date: 2004/04/26 08:28:32; author: jurka; state: Exp; lines: +4 -1
Update the build.xml file to support building with the new 1.5 jdk
and ant 1.6.
Could you be more specific with the version of an
; row.
>
This has been fixed in both the 7.4 and 7.5 cvs versions. Sorry for the
delay, I originally thought the problem was more complicated as described
in my response to another complaint of the same issue here:
http://archives.postgresql.org/pgsql-bugs/2004-06/msg00055.
On Fri, 11 Jun 2004, Kris Jurka wrote:
> On Tue, 8 Jun 2004 [EMAIL PROTECTED] wrote:
>
> > JDBC Driver : PostgreSQL 7.4 (Build 213)
> >
> > I am having an issue with the driver when I do a deleteRow using a
> > ResultSet reco
of places, but perhaps that's the
only way to go.
Kris Jurka
---(end of broadcast)---
TIP 8: explain analyze is your friend
t a valid solution as replaceAll is a 1.4 jdk feature while this
code is in the jdbc2 package which means it must be compilable with the
1.2 jdk. Additionally it's possible for a tablename to contain a
semi-colon. I've been discussing the failings of parseQuery with another
user here:
http://gborg.p
table and development cvs trees and will
be included with the next release. Thanks for the report.
Kris Jurka
---(end of broadcast)---
TIP 1: subscribe and unsubscribe commands go to [EMAIL PROTECTED]
nt
from the 1.4 jdk so I didn't encounter the problem. An upgrade to ant 1.6
definitely shows the problem though.
Kris Jurka
---(end of broadcast)---
TIP 7: don't forget to increase your free space map settings
's name ie MYTABLE won't match
mytable. Another thing to try would be to put just "%" as the table name
and see what happens.
Kris Jurka
---(end of broadcast)---
TIP 8: explain analyze is your friend
imetz. The fix for this is a little
complicated as the date/time/timestamp parsing is kind of messy, but I
will try to have a patch for this sometime this weekend.
Kris Jurka
---(end of broadcast)---
TIP 1: subscribe and unsubscribe commands go to [EMAIL PROTECTED]
l is failing with the error
that there is an open connection to template1. In your case I wonder if
even though the "createdb management" client has exited allowing the code
to proceed to "createdb test" call, the backend associated with this
connection may not hav
> /var/log/pgsqld.log -o -i
>
>
>
> /usr/local/pgsql/bin/createdb management <-- fails here
>
> /usr/local/pgsql/bin/createdb test <-- fails here
>
>
>
>
>
> Any help on what's causing this behavior and how to fix is appreciated.
>
>
>
> -Allen
>
>
>
>
>
>
>
> +=
cle's product supports
postgresql. If it is supposed to support pg, then the place to file the
bug report would be oracle, not here. Because it uses JDBC you can
probably get a connection to any database, but that doesn't mean it will
actually work.
Kris Jurka
---(e
t and
readObject. This problem also occurs in SimpleDataSource. I've
attached the patch I've applied to the gborg cvs repository.
Thanks for the report.
Kris Jurka
? doc
? mine.pdf
? mybuild.xml
Index: org/postgresql/jdbc2/optional/BaseDataSource.java
=
On 16 Jan 2004, Martin Holz wrote:
> Kris Jurka <[EMAIL PROTECTED]> writes:
>
> > On Wed, 7 Jan 2004, Martin Holz wrote:
> >
> > > Hello,
> > >
> > > org.postgresql.jdbc1.AbstractJdbc1Statement.setBinaryStream()
> > > in postgresql 7.4
where it is?
Kris Jurka
---(end of broadcast)---
TIP 6: Have you searched our list archives?
http://archives.postgresql.org
class involved which does not
exist in either the 7.3 or 7.4 drivers. You may have an old version
somewhere in your classpath.
Kris Jurka
---(end of broadcast)---
TIP 8: explain analyze is your friend
ituation
where the Stream was longer than the given length.
Kris Jurka
---(end of broadcast)---
TIP 4: Don't 'kill -9' the postmaster
On Mon, 12 Jan 2004, Neil Conway wrote:
> Tom Lane <[EMAIL PROTECTED]> writes:
> > Kris Jurka <[EMAIL PROTECTED]> writes:
> >> When the JDBC driver tries to query the information schema running against
> >> cvs head, it gets an assertion failure.
>
en be
read as a special character.
It also allows DELIMITER and NULL to overlap. No character in the NULL
specification should be the DELIMITER.
Kris Jurka
DROP TABLE copytest;
CREATE TABLE copytest (a text, b text);
INSERT INTO copytest VALUES ('t,n,g','a');
INSERT INTO c
When the JDBC driver tries to query the information schema running against
cvs head, it gets an assertion failure. The query in question is the
ugly:
SELECT NULL AS TABLE_CAT, n.nspname AS TABLE_SCHEM, c.relname AS
TABLE_NAME, CASE n.nspname LIKE 'pg\\_%' OR n.nspname =
'information_schema' WH
On Fri, 9 Jan 2004, Martin Holz wrote:
> On Friday 09 January 2004 09:46, Kris Jurka wrote:
>
> > The odd thing about the javadocs is that they say "The data will be
> > read from the stream as needed until end-of-file is reached." The
> > length parameter&#x
oblem with positive and negative infinity, but
there are some more problems as evidenced by the attached test case.
Double.MIN_VALUE will cause underflow.
Double.MAX_VALUE goes in alright, but comes out as POSITIVE_INFINITY
when trying Float.MAX_VALUE and MIN_VALUE on a real or float4 field they
ove
length argument is just
for informational purposes and should not be used to limit the amount of
data actually read from the stream.
Kris Jurka
---(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
that comes up with
anything interesting? (Enable log_statement in postgresql.conf and
restart the server making sure the output is going somewhere other than
/dev/null)
What do you get from the results of the following queries when run in
psql?
SELECT version();
SELECT pg_encoding_to_char(1);
SELECT ge
. Just
putting it in a standard location (Debian uses /usr/share/java for all
jars) is fine so other people/packages can adjust their classpath to use
it or symlink it to another location.
Kris Jurka
---(end of broadcast)---
TIP 5: Have you checke
On Fri, 19 Dec 2003, Lamar Owen wrote:
> On Friday 19 December 2003 01:27 pm, Kris Jurka wrote:
> > The RPMs do not have the correct jar file. Try one of those available
> > from http://jdbc.postgresql.org/download.html
>
> At the time I put the RPMs together there were
e /usr/share/pgsql/devpgjdbc3.jar?
The RPMs do not have the correct jar file. Try one of those available
from http://jdbc.postgresql.org/download.html
Kris Jurka
---(end of broadcast)---
TIP 8: explain analyze is your friend
ategorie 1
>
>
> Output after Update
>
> Kunde null
> PLZ/Ort 6 null
> Straße null
> Kategorie 0
>
Here's a patch to fix this.
Kris Jurka
? src/interfaces/jdbc/org/postgresql/copy
? src/interfaces/jdbc/org/postgresql/jdbc2/.AbstractJdbc2ResultSet.java.swp
? src/i
> >>>>> at
> >>>>> com.mphasis.give.common.utilities.DatabaseUtil.getConnection(DatabaseUtil.java:46)
> >>>>> at com.mphasis.give.payment.CartDAO.addToCart(CartDAO.java:161)>>>>>
>
> >>>>>We are usi
1Resu
> ltSet.java:102)
> at
This problem was fixed nearly three months ago in a patch from Kim Ho, but
unfortunately the builds on jdbc.postgresql.org have not been updated in
some time. This fix is in the 7.4 and HEAD cvs branches, but a source
build is t
. Not that a one liner needs one,
but less work for the committers as well as getting it to the JDBC list.
Kris Jurka
? src/interfaces/jdbc/blob_testoutput
? src/interfaces/jdbc/org/postgresql/test/jdbc2/ResultSetMetaDataTest.java
Index: src/interfaces/jdbc/org/postgr
hould only be one error.
Is there any chance you started the postmaster in the background and then
started psql on the same terminal so you get one error reported to the
server and one to the client?
Kris Jurka
---(end of broadcast)---
TIP 8: explain analyze is your friend
this. Additionally the on delete rule would not
return importedKeyRestrict because of a missing if statement. Also an
addition to the test suite is attached.
Kris Jurka
Index: src/interfaces/jdbc/org/postgresql/test/jdbc2/DatabaseMetaDataTest.java
===
Half of this bug was fixed at some point, but an exception is still thrown
when calling rs.afterLast() and then rs.previous(). Attached is a
regression test addition and the appropriate fix. Sorry for the extreme
delay in response and thanks for the thorough report.
Kris Jurka
On Fri, 24 Jan
wrong. Most of the time,
> I actually get 0 results.
The problem is that random() is evaluated on each line giving a different
result.
Kris Jurka
---(end of broadcast)---
TIP 3: if posting/reading through Usenet, please send an appropriate
find your
suggestion has been implemented.
Kris Jurka
---(end of broadcast)---
TIP 1: subscribe and unsubscribe commands go to [EMAIL PROTECTED]
This behavior is present in 7.3 as well.
On Thu, 5 Dec 2002, Kris Jurka wrote:
> Using the old < 7.3 version of dblink on 7.4devel gives a
> "get_names_for_var: bogus varno 5" error.
>
> Install the deprecated version of dblink by following the directions in
> th
Using the old < 7.3 version of dblink on 7.4devel gives a
"get_names_for_var: bogus varno 5" error.
Install the deprecated version of dblink by following the directions in
the dblink.sql file to comment / uncomment various parts of the script.
DROP TABLE t1;
CREATE TABLE t1 (a int);
DROP TABLE t
The following script crashes 7.4devel.
SET geqo_threshold=2;
CREATE TABLE t1 (a int primary key);
CREATE TABLE t2 (a int);
SELECT * FROM t1,t2 WHERE t1.a=t2.a;
#0 0x0811001c in best_inner_indexscan (root=,
rel=,
outer_relids=, jointype=) at
indxpath.c:1421
1421if (samese
101 - 200 of 203 matches
Mail list logo
