hi everyone
i see an attribute 'oid_value' with 'Oid' type in
the ListCell union.
can anyone tell me what does it represents?
Thank you
__
Do you Yahoo!?
Yahoo! Mail - Easier than ever with enhanced search. Learn more.
On Mon, 2004-12-06 at 00:29 -0800, Sibtay Abbas wrote:
i see an attribute 'oid_value' with 'Oid' type in
the ListCell union.
can anyone tell me what does it represents?
Given a linked list of type T_OidList, oid_value holds the data in a
node of the list. Although int_value and oid_value are
hello
i am trying to understand the source code of
postgresql.
Whenever a user enters a query, whether from the
Socket end or the interactive back end, which function
is always invoked that would start manipulation of
that query...
i ve noticed that the primitive parsing is done by the
On Mon, 6 Dec 2004, ElayaRaja S wrote:
I am using postgresql-7.4.5. I nee to use the jdbc connection So i
downloaded 4 versions of driver( pg74.215.jdbc1.jar,
pg74.215.jdbc2.jar, pg74.215.jdbc2ee.jar, pg74.215.jdbc3.jar). I am
uanble to connect it. Please let me know which version of
On Mon, 6 Dec 2004 00:27:18 -0500 (EST), [EMAIL PROTECTED]
[EMAIL PROTECTED] wrote:
Hello,
A short note that I've updated DBD::PgSPI version 0.02 to CPAN.
There are no new features - but the code now expects (and works with)
reasonably decent versions of perl (5.8.x) and pgsql (8.x).
Just
On Mon, 6 Dec 2004, Mike Rylander wrote:
Just so that you have some info, I've been using DBD::PgSPI with Pg 8.0
since beta 1. The only restriction I've run into with the old code is
that it doesn't like the DBD 'do' method. I have to use execute/fetchX
or selectX, but other than that it
On Mon, 6 Dec 2004 08:17:29 -0500 (EST), [EMAIL PROTECTED]
[EMAIL PROTECTED] wrote:
On Mon, 6 Dec 2004, Mike Rylander wrote:
Just so that you have some info, I've been using DBD::PgSPI with Pg 8.0
since beta 1. The only restriction I've run into with the old code is
that it doesn't like
On Mon, 6 Dec 2004, Mike Rylander wrote:
With v. 0.01 the statement just doesn't seem to execute. I know that's
odd, because it's supposed to be doing a prepare/execute internally, but
nothing happens.
Wierd - the testsuite (make test) has some 'dos' in the code and it works
(and it checks
OSDL provides hardware. You have to sign up for a login here:
https://www.osdl.org/join_form
And submit a project proposal here:
https://www.osdl.org/lab_activities/lab_projects/a_propose_project/propose_a_project.html
Mark
---(end of
I tried compliling v8 beta 5 (grabbed from cvs on Friday) on AIX 5.1.
It fails during the make
make[4]: Entering directory
`/opt/OXRS/Sources/pgsql-HEAD/src/interfaces/libpq'
make[4]: Nothing to be done for `all'.
make[4]: Leaving directory
`/opt/OXRS/Sources/pgsql-HEAD/src/interfaces/libpq'
Brad Nicholson wrote:
I tried compliling v8 beta 5 (grabbed from cvs on Friday) on AIX 5.1.
It fails during the make
make[4]: Entering directory
`/opt/OXRS/Sources/pgsql-HEAD/src/interfaces/libpq'
make[4]: Nothing to be done for `all'.
make[4]: Leaving directory
Just compiled RC1 on a netwinder ARM system running Debian Linux (sarge). All
tests passed except point with the
following in results/point
Jim
--
-- POINT
--
CREATE TABLE POINT_TBL(f1 point);
INSERT INTO POINT_TBL(f1) VALUES ('(0.0,0.0)');
INSERT INTO POINT_TBL(f1) VALUES ('(-10.0,0.0)');
Would you send us regression.diff? That should show the differences.
---
Jim Buttafuoco wrote:
Just compiled RC1 on a netwinder ARM system running Debian Linux (sarge).
All tests passed except point with the
Bruce Momjian wrote:
Brad Nicholson wrote:
I tried compliling v8 beta 5 (grabbed from cvs on Friday) on AIX 5.1.
It fails during the make
make[4]: Entering directory
`/opt/OXRS/Sources/pgsql-HEAD/src/interfaces/libpq'
make[4]: Nothing to be done for `all'.
make[4]: Leaving directory
See attached
-- Original Message ---
From: Bruce Momjian [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Cc: pgsql-hackers [EMAIL PROTECTED]
Sent: Mon, 6 Dec 2004 12:24:18 -0500 (EST)
Subject: Re: [HACKERS] arm rc1 regression failures
Would you send us regression.diff? That should
On Tue, Nov 30, 2004 at 10:51:42PM +, Simon Riggs wrote:
My suggestion: increase checkpoint_timeout to 600 secs, increase
bgwriter parameters also, to reduce how frequently it is called, as well
as increase the number of blocks per cycle.
Ok, here are a series of three tests varying the
Mark,
Ok, here are a series of three tests varying the bgwriter_delay at 1,
50, and 100:
http://www.osdl.org/projects/dbt2dev/results/pgsql/bgwriter_delay/
Hmmm. Looks inconclusive. The differences between the runs are 0.3%,
which is a margin of error by anyone's definition.
Brad Nicholson wrote:
OK, I assume you used --enable-thread-safety in configure.
Correct.
This should
have added some PTHREAD link flags to your libpq build, and those
settings should have followed the libpq library into your pg_ctl link
line.
Would you look in your Makefile.global
Brad Nicholson wrote:
I tried compliling v8 beta 5 (grabbed from cvs on Friday) on AIX 5.1.
I see now you are running AIX 5.1. Is that a fairly modern/popular
version of AIX?
--
Bruce Momjian| http://candle.pha.pa.us
[EMAIL PROTECTED] | (610)
On Mon, Dec 06, 2004 at 08:17:29AM -0500, [EMAIL PROTECTED] wrote:
I put a version of code with a bit more fixes from comments onlist to
www.pilosoft.com/PgSPI/DBD-PgSPI-0.03pre.tar.gz
After correcting the path (no directory) I downloaded this and it
built without changes on FreeBSD
Jim Buttafuoco wrote:
See attached
Well, that test passed for the last release, so what changed in between?
I don't think we changed the floating-point output again, did we?
--
Peter Eisentraut
http://learn.to/quote
---(end of broadcast)---
BTW, I would like to get these capabilities into core plperl.
There are some obstacles to overcome. For example:
. not every perl installation has DBI
. how to turn it on for trusted plperl
. DBD::PgSPI is covered by GPL, which means it can't be used in the core
distribution of postgres - we'd
On Mon, 6 Dec 2004, Andrew Dunstan wrote:
BTW, I would like to get these capabilities into core plperl.
There is already spi_exec_query in pl/perl for quick and dirty DB access
for this purpose, no?
There are some obstacles to overcome. For example:
. not every perl installation has DBI
On Mon, Dec 06, 2004 at 11:44:20AM -0700, Michael Fuhr wrote:
After correcting the path (no directory) I downloaded this and it
built without changes on FreeBSD 4.10-STABLE and Solaris 9, both
running PostgreSQL 8.0.0rc1 and Perl 5.8.6. However, something
changed since 0.02 that broke
[EMAIL PROTECTED] writes:
On Mon, 6 Dec 2004, Andrew Dunstan wrote:
. how to turn it on for trusted plperl
Eh, you don't turn it on. You install the package and it works ;)
Really? If the plperl Safe opmask allows that, we've got some problems.
regards, tom lane
On Mon, 6 Dec 2004, Tom Lane wrote:
[EMAIL PROTECTED] writes:
On Mon, 6 Dec 2004, Andrew Dunstan wrote:
. how to turn it on for trusted plperl
Eh, you don't turn it on. You install the package and it works ;)
Really? If the plperl Safe opmask allows that, we've got some problems.
On Mon, 2004-12-06 at 17:43, Josh Berkus wrote:
Mark,
Ok, here are a series of three tests varying the bgwriter_delay at 1,
50, and 100:
http://www.osdl.org/projects/dbt2dev/results/pgsql/bgwriter_delay/
Hmmm. Looks inconclusive. The differences between the runs are 0.3%,
[EMAIL PROTECTED] wrote:
. DBD::PgSPI is covered by GPL, which means it can't be used in the core
distribution of postgres - we'd have to reinvent it in a clean room fashion.
Actually, its both GPL and Artistic license - identical to DBD::Pg (where
most of the code is taken from).
I don't
On Mon, 6 Dec 2004, Andrew Dunstan wrote:
I disagree. The crucial difference is that DBD::Pg is a client side
library and plperl is not.
I would like all perl programmers to be able to use the same (or
similar) idioms on both the client side and the server side. (Just as
one can use JDBC
Hi Tom + *,
Am 03.12.2004 um 23:58 schrieb Tom Lane:
schmidtm [EMAIL PROTECTED] writes:
is somebody working on these two issues on the TODO-List?
1) Prevent default re-use of sysids for dropped users and groups
I don't know of anyone actively working on it, but if you check the
archives you'll
On Mon, Dec 06, 2004 at 02:34:33PM -0500, [EMAIL PROTECTED] wrote:
For quick access from trusted code, spi_exec should just do fine.
BTW, does stock PL/Perl have functions for escaping identifiers,
strings, and binary strings?
--
Michael Fuhr
http://www.fuhr.org/~mfuhr/
On Mon, 6 Dec 2004, Michael Fuhr wrote:
On Mon, Dec 06, 2004 at 02:34:33PM -0500, [EMAIL PROTECTED] wrote:
For quick access from trusted code, spi_exec should just do fine.
BTW, does stock PL/Perl have functions for escaping identifiers,
strings, and binary strings?
non-DBI? no.
DBI?
On Mon, Dec 06, 2004 at 03:02:45PM -0500, [EMAIL PROTECTED] wrote:
On Mon, 6 Dec 2004, Michael Fuhr wrote:
On Mon, Dec 06, 2004 at 02:34:33PM -0500, [EMAIL PROTECTED] wrote:
For quick access from trusted code, spi_exec should just do fine.
BTW, does stock PL/Perl have functions
Michael Fuhr wrote:
DBI? yes, $pg_dbh-quote('foo')
Yeah, I know about DBI, but since we currently can't use it in
trusted code I was wondering what we *could* use. With DBI I'd be
using placeholders wherever possible, but unless I've missed something
spi_exec_query() requires values to be
On Sun, Dec 05, 2004 at 04:06:57PM -0500, Andrew Dunstan wrote:
Amen, brother! That would never be tolerated in any commercial setting
that I am aware of, and should not be here either, IMNSHO. Silence does
I don't know what commercial settings you're familiar with, but I can
think of some
On Mon, Dec 06, 2004 at 04:00:30PM -0500, Andrew Sullivan wrote:
however, certainly explains a number of really crappy pieces of
software I've had to work with.
Uh, that's not a swipe at Bruce -- rather praise for everyone
involved for being frank enough to discuss this.
A
--
Andrew
Bruce Momjian wrote:
Brad Nicholson wrote:
OK, I assume you used --enable-thread-safety in configure.
Correct.
This should
have added some PTHREAD link flags to your libpq build, and those
settings should have followed the libpq library into your pg_ctl link
line.
Would you look
On Mon, 2004-12-06 at 17:42, Mark Wong wrote:
On Tue, Nov 30, 2004 at 10:51:42PM +, Simon Riggs wrote:
My suggestion: increase checkpoint_timeout to 600 secs, increase
bgwriter parameters also, to reduce how frequently it is called, as well
as increase the number of blocks per cycle.
On Mon, Dec 06, 2004 at 01:07:11PM -0500, Bruce Momjian wrote:
I see now you are running AIX 5.1. Is that a fairly modern/popular
version of AIX?
To the extent AIX is popular :) 5.1 is one release behind the very
latest.
A
--
Andrew Sullivan | [EMAIL PROTECTED]
The plural of anecdote is
[EMAIL PROTECTED] writes:
On Mon, 6 Dec 2004, Andrew Dunstan wrote:
. how to turn it on for trusted plperl
[ snip ]
Errr my bad. I keep confusing trusted/untrusted. It does not allow it, nor
should it.
The purpose of PgSPI is to write 'middleware' solutions in perl - the idea
is that
On Mon, 2004-12-06 at 21:59, Andrew Sullivan wrote:
On Mon, Dec 06, 2004 at 01:07:11PM -0500, Bruce Momjian wrote:
I see now you are running AIX 5.1. Is that a fairly modern/popular
version of AIX?
To the extent AIX is popular :) 5.1 is one release behind the very
latest.
AIX 5.3 is
On Mon, 6 Dec 2004, Tom Lane wrote:
Sure. But you don't run your middleware as root (I hope ;-)) and you
shouldn't run it in untrusted server-side languages either. I agree
Actually - I don't practically care, and in fact I'm doing things that are
unsafe...But, I agree, others may think
schmidtm [EMAIL PROTECTED] writes:
Do I get that right: the only reason to do max(sysid) or a
user-supplied ID in CreateUser() (commands/user.c) is that we don't
have the ability to get sequences over the *.BKI/initdb mechanism?
No, that's not quite the direction of the problem. The real
There was some talk of branching REL8_0_STABLE after 8.0.0rc1 was
released. Is that still the plan?
TIA,
Neil
---(end of broadcast)---
TIP 8: explain analyze is your friend
On Mon, Dec 06, 2004 at 09:28:15PM +, Simon Riggs wrote:
Mark,
Few questions:
- can we put the logging to DEBUG1 please, so we can see the
checkpoints? ...and set debug_shared_buffers = 10
Ok, will do.
I don't understand why the checkpoints are so regular at 300 seconds if
the
Simon Riggs wrote:
On Mon, 2004-12-06 at 21:59, Andrew Sullivan wrote:
On Mon, Dec 06, 2004 at 01:07:11PM -0500, Bruce Momjian wrote:
I see now you are running AIX 5.1. Is that a fairly modern/popular
version of AIX?
To the extent AIX is popular :) 5.1 is one release behind the
On Mon, 2004-12-06 at 23:18, Mark Wong wrote:
On Mon, Dec 06, 2004 at 09:28:15PM +, Simon Riggs wrote:
Mark,
Few questions:
Thanks.
On the graphs... why do the graphs for Proc Utilisation, Index Scans
etc, only show first 300 secs of a 3600 sec long run? Are those axes
correct? (I
Bruce Momjian [EMAIL PROTECTED] writes:
OK, so does someone want to suggest why a library used to link libpq
would also be needed to link binaries that use libpq?
No doubt because it's one of those platforms where shared libraries
don't carry their own dependency information. AFAICS,
On Mon, Dec 06, 2004 at 11:44:22PM +, Simon Riggs wrote:
On the graphs... why do the graphs for Proc Utilisation, Index Scans
etc, only show first 300 secs of a 3600 sec long run? Are those axes
correct? (I understand seeing the ramp-up is important, I just want to
check the time axis).
I have started filling in the supported platform list for the 8.0.0
release with the information from the build farm:
http://developer.postgresql.org/docs/postgres/supported-platforms.html
It's now time to fill the holes. Briefly, I'm looking for exit status 0
on
./configure
Bruce Momjian wrote:
OK, so does someone want to suggest why a library used to link libpq
would also be needed to link binaries that use libpq? And with no
cc_r it seems I have no idea how to get this working.
We didn't get this working for 7.4, for reasons that we are again
becoming aware
Neil Conway [EMAIL PROTECTED] writes:
There was some talk of branching REL8_0_STABLE after 8.0.0rc1 was
released. Is that still the plan?
I'm up for it, personally --- is everybody else ready? Should we wait
another day or three?
regards, tom lane
headsup courtesy of buildfarm.
problems apparently with NaNs, infinities and negative zeros.
see:
http://www.pgbuildfarm.org/cgi-bin/show_log.pl?nm=fantaildt=2004-12-06%2011:05:24
cheers
---(end of broadcast)---
TIP 9: the planner will ignore your
Peter Eisentraut wrote:
I have started filling in the supported platform list for the 8.0.0
release with the information from the build farm:
http://developer.postgresql.org/docs/postgres/supported-platforms.html
It's now time to fill the holes. Briefly, I'm looking for exit status 0
on
On Mon, Dec 06, 2004 at 12:53:52PM -0500, Bruce Momjian wrote:
Brad Nicholson wrote:
OK, I assume you used --enable-thread-safety in configure.
Correct.
This should
have added some PTHREAD link flags to your libpq build, and those
settings should have followed the libpq library
On Mon, 6 Dec 2004, Tom Lane wrote:
Neil Conway [EMAIL PROTECTED] writes:
There was some talk of branching REL8_0_STABLE after 8.0.0rc1 was
released. Is that still the plan?
I'm up for it, personally --- is everybody else ready? Should we wait
another day or three?
Let's say Friday I branch her
Peter Eisentraut wrote:
Bruce Momjian wrote:
OK, so does someone want to suggest why a library used to link libpq
would also be needed to link binaries that use libpq? And with no
cc_r it seems I have no idea how to get this working.
We didn't get this working for 7.4, for reasons that
Kenneth Marshall wrote:
Let me ask --- if you change the CC line in Makefile.global to cc_r,
does everything build OK? That might be a clean solution because the
change could be made in one place. Of course this would mean the
backend would also be compiled using cc_r and I have no idea
Sorry, here is select version();
PostgreSQL 8.0.0rc1 on i386-pc-bsdi4.3.1, compiled by GCC 2.95.3
---
Peter Eisentraut wrote:
I have started filling in the supported platform list for the 8.0.0
release with
==
All 96 tests passed.
==
version
PostgreSQL 8.0.0rc1 on i386-unknown-freebsd5.3, compiled by GCC gcc (GCC)
Bruce Momjian [EMAIL PROTECTED] writes:
However, one thing we can do is to try this in Makefile.aix:
# AIX needs threads for everything that uses libpq
LIBS += $(PTHREAD_LIBS)
That is going to enable thread libs for all linking including the
backend, but it might work.
That is
Andrew Dunstan [EMAIL PROTECTED] writes:
Peter Eisentraut wrote:
./configure --prefix=SOMEWHERE --enable-thread-safety --with-tcl \
--with-perl --with-python --with-krb5 --with-pam -with-openssl
make
make install
make check
buildfarm actually runs in this order:
make
make check
make
hi
is Procedural language handler function the
interface for adding your own procedural languages to
postgres?
I ve read the documentation but i am not able to
understand where do we deal with stuff like parse
trees, query trees, plan trees etc.
Ofcourse any procedural language should pass
Sibtay,
hi
is Procedural language handler function the
interface for adding your own procedural languages to
postgres?
I ve read the documentation but i am not able to
understand where do we deal with stuff like parse
trees, query trees, plan trees etc.
Ofcourse any procedural language should pass
Tom Lane said:
Andrew Dunstan [EMAIL PROTECTED] writes:
Peter Eisentraut wrote:
./configure --prefix=SOMEWHERE --enable-thread-safety --with-tcl \
--with-perl --with-python --with-krb5 --with-pam -with-openssl
make
make install
make check
buildfarm actually runs in this order:
make
i guess the answer to my previous question was spi...i
ve got another question, can we call pgsql or plpgsql
functions using spi?
like can we do something like
SPI_execute(CREATE FUNCTION blah() RETURNS Integer
.
__
Do you Yahoo!?
66 matches
Mail list logo
