Tom Lane wrote:
A Bind/Execute facility would need a pair of routines with signatures
very similar to PQexecParams/PQsendQueryParams --- they'd take a
prepared statement name instead of a query string, and they'd not need
an array of parameter type OIDs, but otherwise the same. I couldn't
come up
Larry Rosenman <[EMAIL PROTECTED]> writes:
> Nope. There is no .psqlrc.
> It seems to be new with 7.4cvs. (dunno about earlier 7.4), but it definitely
> did NOT happen with 7.3.x
Hmph. There have been some changes in 7.4 psql's pager support, but I
can't see anything there that looks like it wo
Hi everybody
It's my first post here, so be indulgent ;)
Just to confirm : if i do
$sql1='insert into "Enfant" ("NomEnfant","PrenomEnfant") VALUES
('.$NomEnfant.','.$PrenomEnfant.')
$sql2='insert into "IndividuEnfant" ("IdIndividu","IdEnfant") VALUES
('.$IdIndividu.',currval(\'"Enfant_Seq"\')
"Christopher Kings-Lynne" <[EMAIL PROTECTED]> writes:
>> We could also think about providing an interface to do just Parse,
>> although this is inessential since you can set up a prepared statement
>> by PQexec'ing a PREPARE command.
> Wait just a minute! phpPgAdmin would love to be able to 'pars
Stephen Frost <[EMAIL PROTECTED]> writes:
> You probably know but I'll quickly outline it to point out the
> differences, as I see them, from the 'COPY' ability. Basically the user
> defines their own C structure and then malloc's an array of them. The
> user then tells the database the type, off
Gmane Smith <[EMAIL PROTECTED]> writes:
> Using
>Mac OS X 10.2.6
>Pgsql 7.4 (postgresql-7.4beta1) from postgresql.org
>devpgjdbc2.jar
> and WebObjects 5.2
> I get
>LOG: invalid message length
You should probably report this to pgsql-jdbc; it sounds like a flaw in
their implement
> This leaves us with a bit of a problem, though, because there isn't
> any libpq API that allows access to this speedup. I put in a
> routine to support Parse/Bind/Execute so that people could use
> out-of-line parameters for safety reasons --- but there's no
> function to do Bind/Execute against
Gavin Sherry <[EMAIL PROTECTED]> writes:
> On Tue, 12 Aug 2003, Andrew Dunstan wrote:
>> Is this a security hole? Looks like one to me. Would it be better to use
>> a sequence generator for sysids instead of using max+1 on the user
>> table? Or else store the last sysid used somewhere?
> This is
--On Tuesday, August 12, 2003 09:30:39 -0400 Tom Lane <[EMAIL PROTECTED]>
wrote:
Larry Rosenman <[EMAIL PROTECTED]> writes:
Nope. There is no .psqlrc.
It seems to be new with 7.4cvs. (dunno about earlier 7.4), but it
definitely did NOT happen with 7.3.x
Hmph. There have been some changes in
Hi,
When a trigger event occurs, how does the trigger manager(called by the
Executor) set up TriggerData(tg_event in particular) information structure
before calling the trigger function to handle the event. Is the detail
available in any system table?
Googling and the documentation search does n
"Christopher Kings-Lynne" <[EMAIL PROTECTED]> writes:
> I notice on the SET CONSTRAINTS doc page, it says SET CONSTRAINTS
> ...
> But it doesn't at all make it clear what is, since cosntraint
> names are per-relation I thought?
Looking at the code, it will set the mode for *all* FKs with the sam
Andrew Dunstan writes:
> Makes sense, but I think DROP USER should also warn immediately if it
> detects the most common case (I imagine) where the user owns things in
> the current database.
Well, the "dropuser" program connects to template1, so in that case it'd
be a rather uncommon occurrence.
On Wed, 13 Aug 2003, Christopher Kings-Lynne wrote:
> Hi,
>
> I notice on the SET CONSTRAINTS doc page, it says SET CONSTRAINTS
> ...
>
> But it doesn't at all make it clear what is, since cosntraint
> names are per-relation I thought?
It's a constraint name. IIRC, it happens to affect all su
[ Moved to hackers.]
Tom Lane wrote:
> Bertrand Petit <[EMAIL PROTECTED]> writes:
> > Non superusers can set log_statement to true but can't set it
> > back to false even if log_statement was false at the begining of a
> > connection.
>
> Yeah. I think that the restrictions for USERLIMIT va
> > Wait just a minute! phpPgAdmin would love to be able to 'parse' arbitrary
> > sql entered by the user to separate semi-coloned queries, identify various
> > types of queries, etc. What would a Parse call allow us to do?
>
> Hm. I was about to say "very little that you can't do with a PREPARE
Oleg Bartunov kirjutas E, 11.08.2003 kell 11:52:
> On Mon, 11 Aug 2003, Peter Eisentraut wrote:
>
> > Alexey Mahotkin writes:
> >
> > > AFAIK, currently the codepoints are sorted in their numerical order. I've
> > > searched the source code and could not find the actual place where this is
> > >
Rahul_Iyer kirjutas K, 13.08.2003 kell 08:23:
> hi...
> im on a project using Postgres. The project involves, at times, upto
> 5,000,000 inserts. I was checking the performance of Postgres for 5M inserts
> into a 2 column table (one col=integer, 2nd col=character). I used the
> Prepare... and execu
Bruce Momjian <[EMAIL PROTECTED]> writes:
> Yes, I have been thinking of that. The big question is whether a
> non-super user can control the reset value?
He could (via PGOPTIONS) ... but since he can only increase it, there is
nothing to fear.
regards, tom lane
Regarding second item, I don't think anyone suggested autodropping
objects, or else I misunderstood. (That would be dangerous, to say the
least, IMHO). There were suggestions of reparenting objects, and warning
of objects losing ownership, although feasibility questions remain.
(I'm still co
Bruce Momjian <[EMAIL PROTECTED]> writes:
> Can I have a TODO for this?
* Prevent accidental re-use of sysids for dropped users and groups
The other part of the thread was something like
* Prevent dropping user that still owns objects, or auto-drop the objects
which if successful would eliminat
Hi all,
I have produced some code coverage data using gcov + ltp to show which
parts of the source code the regression tests are hitting and which parts
they aren't. The results are at: http://www.alcove.com.au/pgregress/
Thanks,
Gavin
---(end of broadcast)-
On Tue, 12 Aug 2003, Christopher Kings-Lynne wrote:
> > > rbt=3D# ALTER USER rbt SET CONSTRAINTS ALL DEFERRED;
> > > ERROR: syntax error at or near "ALL" at character 32
> > > rbt=3D# ALTER USER rbt SET CONSTRAINTS =3D DEFERRED;
> > > ERROR: "constraints" is not a recognized option
> >
> > "SET
* Tom Lane ([EMAIL PROTECTED]) wrote:
> Of course the obvious way of getting rid of the parser overhead is not
> to parse everytime --- viz, to use prepared statements.
I think this would be nice to have too... On a similar note (I think
anyway) I wasn't able to find any functions for bulk dumps
I know. It just makes a few things a pain if you can't say "I know this
character can't be part of that".
Nevermind. Just wishful thinking. I'll shut up now.
andrew
Christopher Kings-Lynne wrote:
Seriously, I think there's a good case for banning a few characters in
at least some names - like
Below is output from 7.3 pg_dump that is being loaded into 7.4 beta1.
It would seem that revoking the permissions of the owner doesn't work
out so well.
r=# CREATE FUNCTION weekdate (date) RETURNS timestamp with time zone
r-# AS '
r'# SELECT cast(to_date(''01 01 ''|| extract(''year'' FROM $1
Stephen Frost <[EMAIL PROTECTED]> writes:
> ... If libpq grabs the entire result in one go then that may
> actually cause a problem for me when I start to move things from Oracle
> to postgres since the clients don't always have much memory available.
It does that in an ordinary SELECT. The custo
I said:
> I doubt a hash is worth maintaining, because the active tabstat entries
> should only be for tables that are being touched in the current command
> (thus, there are not more than six in your example). I'm not sure why
> it takes so much time to look through six entries though ...
I repl
Oh yea, I'm running 7.3.3 on Redhat 7.3.
--Nate
---(end of broadcast)---
TIP 5: Have you checked our extensive FAQ?
http://www.postgresql.org/docs/faqs/FAQ.html
Tom Lane wrote:
> Bruce Momjian <[EMAIL PROTECTED]> writes:
> > /* Limit non-superuser changes */
> > if (record->context == PGC_USERLIMIT &&
> > source > PGC_S_UNPRIVILEGED &&
> > newval < conf->session_val &&
>^^^
>
I did some basic profiling of CVS HEAD after having read Bruce's post the
other day: When did we get so fast. It seemed to me that the number of
inserts per second wasn't actually all that high so I had a look at some
numbers:
% cumulative self self total
time seconds s
elein <[EMAIL PROTECTED]> writes:
> configure knows it is a linux box.
> Should it be trying to link to libwsock32.so
> or not? If this is a legitimate link, then
> the problem is different than if it is trying
> to link it in erroneously.
configure is unconditionally including libwsock32 if it c
On Wed, 13 Aug 2003 10:53:39 +0530
"Rahul_Iyer" <[EMAIL PROTECTED]> wrote:
> hi...
> im on a project using Postgres. The project involves, at times, upto
> 5,000,000 inserts. I was checking the performance of Postgres for 5M
> inserts into a 2 column table (one col=integer, 2nd col=character). I
>
> im on a project using Postgres. The project involves, at times, upto
> 5,000,000 inserts. I was checking the performance of Postgres for 5M inserts
> into a 2 column table (one col=integer, 2nd col=character). I used the
> Prepare... and execute method, so i basically had 5M execute statements an
--On Friday, August 08, 2003 02:10:25 -0400 Bruce Momjian
<[EMAIL PROTECTED]> wrote:
Actually, your getpwuid_r is the old, pre-POSIX format. The attached
email has the configure tests. I was hoping we wouldn't need them, but
it seems we may.
Err, SCO claims SUSv2, the Single Unix Specificatio
> could be \dn for describe namespace for ei : \dn pg_catalog,
> or only \dn to list all namespaces
Already done in CVS...
Chris
---(end of broadcast)---
TIP 7: don't forget to increase your free space map settings
I just (with the last half hour) grabbed a fresh copy of 7.4 from CVS
and got an error when building contrib/array:
gcc -O2 -Wall -Wmissing-prototypes -Wmissing-declarations -fpic -I.
-I../../src/include -c array_iterator.c -o array_iterator.o
array_iterator.c:30: utils/fmgroids.h: No such file
I blame SuSE.
Thank you for the fix and confirmation of the problem.
elein
On Mon, Aug 11, 2003 at 01:53:31PM -0400, Tom Lane wrote:
> elein <[EMAIL PROTECTED]> writes:
> > Yes, I actually have a libwsock32 because my
> > system has wine on it. Wine is a windows
> > emulator.
>
> And they
In an attempt to throw the authorities off his trail, [EMAIL PROTECTED] (Bruno Wolff
III) transmitted:
> On Fri, Aug 08, 2003 at 15:32:05 +0530,
> Rahul_Iyer <[EMAIL PROTECTED]> wrote:
>> hi, im currently working on a project that requires batch
>> operations - eg. Batch insert/update etc. The d
Christopher Kings-Lynne <[EMAIL PROTECTED]> writes:
> What do you actually get back from a Parse request?
Nothing. If successful, it creates a prepared statement inside the
server.
It might possibly make sense for a libpq routine that exposes Parse
to actually do Parse followed by Describe State
Gavin Sherry <[EMAIL PROTECTED]> writes:
> but pgstat_initstats() caught my eye. This gets called about 6 times per
> insert (I did 10 inserts) and the major cost appears to relate to the
> linear pgStatTabstatMessages. The comparative performance of
> hash_search() suggests that pgStatTabstatM
Hello,
are there any plans of making Postgresql to properly support Unicode wrt
language-specific collations and upper/lower case handling?
AFAIK, currently the codepoints are sorted in their numerical order. I've
searched the source code and could not find the actual place where this is
done.
I ran into an "interestingness" with my 7.4 upgrade/testing.
It seems it's impossible (without editing the dump file), to reload a
pg_dumpall file
that has objects owned by one original user (postgres), into a new DB with
a new
original user (pgsql74).
Just food for someone to think about. (I
> This leaves us with a bit of a problem, though, because there isn't any
> libpq API that allows access to this speedup. I put in a routine to
> support Parse/Bind/Execute so that people could use out-of-line
> parameters for safety reasons --- but there's no function to do
> Bind/Execute against
Kurt Roeckx <[EMAIL PROTECTED]> writes:
> If they don't have it defined, it's not going to do what we
> expect and we might be better of using our replacement functions.
We will if we don't find struct addrinfo. See notes at top of getaddrinfo.h.
regards, tom lane
--
I managed to blow the SCO compiler up again with /contrib/cube. the only
workaround
(from SCO already) is to disable -O on that module.
Fair warning.
LER
--
Larry Rosenman http://www.lerctr.org/~ler
Phone: +1 972-414-9812 E-Mail: [EMAIL PROTECTED]
US Mail: 1
rbt=# ALTER USER rbt SET CONSTRAINTS ALL DEFERRED;
ERROR: syntax error at or near "ALL" at character 32
rbt=# ALTER USER rbt SET CONSTRAINTS = DEFERRED;
ERROR: "constraints" is not a recognized option
signature.asc
Description: This is a digitally signed message part
I am seeing this (RH8 - cvs tip):
2003-08-09 18:55:14 [6680] LOG: failed to create socket: Address family
not supported by protocol
Probably harmless - presumably refers to IPv6 not running, but annoying
nevertheless, and I don't recall seeing it before.
I can still connect on IP4 socket and
Tom Lane wrote:
I'm beginning to think that was a serious omission. I'm tempted to fix
it, even though we're past feature freeze for 7.4. Comments?
Seems pretty well isolated. If you're tallying votes, count me as a "yay".
Joe
---(end of broadcast)-
Sean Chittenden <[EMAIL PROTECTED]> writes:
>> I'm beginning to think that was a serious omission. I'm tempted to
>> fix it, even though we're past feature freeze for 7.4. Comments?
> On a quasi-similar note (and unless I've missed how to do this), you
> can't create a cursor from a prepared sta
Rod Taylor wrote:
-- Start of PGP signed section.
> > Allow SQL200X inheritance syntax LIKE , INCLUDING DEFAULTS?
> (Rod)
>
> Yes, it includes defaults.
OK, updated.
> > > Have COMMENT ON DATABASE on non-local database generate a warning
> (Tom)
> > > I think that was someone else's work ... Rod
* Tom Lane ([EMAIL PROTECTED]) wrote:
> Stephen Frost <[EMAIL PROTECTED]> writes:
> > You probably know but I'll quickly outline it to point out the
> > differences, as I see them, from the 'COPY' ability. Basically the user
> > defines their own C structure and then malloc's an array of them. Th
elein <[EMAIL PROTECTED]> writes:
> This is as far as I've gotten with 7.4.
Would you rebuild with --enable-debug (perhaps also --enable-cassert)
so that the gdb backtrace is more informative?
Also, it seems likely that the issue is in or around the recently-added
IPv6 support, so I'd suggest usi
I am currently reading up on the history behind inheritance in
postgres and found this interesting post back in May
2000.
http://archives.postgresql.org/pgsql-hackers/2000-05/msg01349.php
From reading other posts, it seems that there is the idea
that since under is single i
[EMAIL PROTECTED] writes:
> Aug 7 13:23:30 calchas postgres[27794]: [3] ERROR: simple_heap_update:
> tuple concurrently updated
The only case of this I'm aware of is the concurrent-ANALYZE issue,
which is pretty harmless. But you say it's not that. I'd suggest
turning on log_statement and log_du
"Gaetano Mendola" <[EMAIL PROTECTED]> writes:
> the following code was working properly under Postgres 7.3.X
> I'm now running my regression test with Postgres 7.4beta1 and I'm
> having the error in subj.
I tried this and got
regression=# select bar();
bar
-
0
(1 row)
regression=#
Anyon
(Thought triggered by something Tom said the other day)
Is this a security hole? Looks like one to me. Would it be better to use
a sequence generator for sysids instead of using max+1 on the user
table? Or else store the last sysid used somewhere?
andrew
facetest=# create user blurfl;
CREATE U
> -Original Message-
> From: Christopher Kings-Lynne [mailto:[EMAIL PROTECTED]
> Sent: 11 August 2003 04:02
> To: Andrew Dunstan; Hackers
> Subject: Re: [HACKERS] dropping a user causes pain (#2)
>
>
> DROP USER foo OWNER TO bob;
Isn't that a bit tricky as foo might own objects in ot
Andrew Dunstan wrote:
Regarding second item, I don't think anyone suggested autodropping
objects, or else I misunderstood. (That would be dangerous, to say the
least, IMHO).
I agree, but some applications might use tables dedicated to a specific
user. While this is IMHO not a good style to us
"Christopher Kings-Lynne" <[EMAIL PROTECTED]> writes:
> Ah OK, I must have been thinking of the database owner check. I'd vote for
> (1) checking that they own no objects and by default owning all their stuff
> to the database owner. Plus add an optional clause:
> DROP USER foo OWNER TO bob;
If
--On Tuesday, August 05, 2003 16:41:34 -0400 Tom Lane <[EMAIL PROTECTED]>
wrote:
Larry Rosenman <[EMAIL PROTECTED]> writes:
--On Tuesday, August 05, 2003 16:27:55 -0400 Tom Lane
<[EMAIL PROTECTED]>
A variant (which'd be okay with me) is to separate these fields with
tabs instead of spaces; then
This is caused by sys/socket.h #defining shutdown _shutdown, and already
reported.
I filed the bug last nite, and Tom replied, and my reply is in the thread.
LER
--On Wednesday, August 06, 2003 19:14:49 +0200 [EMAIL PROTECTED] wrote:
Hi all,
I've put my hands on 7.4beta1 and it doesn't compil
Josh Berkus wrote:
> Joe,
>
> > They are done (at least the array declarations and array element
> > assignment part):
>
> Way cool! How'd I miss that one?
>
> Time to test
>
> > >>o Add PL/PgSQL PROCEDURES that can return multiple values
> > >
> > > Hmmm ... I know how this got o
elein wrote:
I thought that statement level triggers did not work yet.
Are they supposed to work in 7.4?
(But even if they don't work they shouldn't crash...)
Yeah, they work - not as everyone would like, but they work. All fixed
now anyway.
Joe
---(end of broadcast)--
On Tue, 2003-08-12 at 15:36, Tom Lane wrote:
> Gavin Sherry <[EMAIL PROTECTED]> writes:
> > I wasn't interested in measuring the performance of yacc -- since I know
> > it is bad. It was a basic test which wasn't even meant to be real
> > world. It just seemed interesting that the numbers were thre
Bruce Momjian <[EMAIL PROTECTED]> writes:
> Adding several new variables is fine, but what do we call the hostname
> option if we already have log_hostname?
We've renamed GUC variables before for consistency. I'd opt
for picking names that show the common purpose, maybe log_line_FOO?
Andrew Dunstan wrote:
I did have a thought that it could be done lazily (on backend startup)
on other databases and immediately on the current database. I guess it
depends on the cost of checking for such things - wouldn't want to add
greatly to startup time.
That would leave a small window of
Robert Creager <[EMAIL PROTECTED]> writes:
> [much data]
Well, I'm baffled. The vacuum process is evidently waiting for the
insert, but I don't think it could be holding any lock that the other
two want. The insert is trying to grab a per-buffer lock, which is
reasonable. I do not see that the
I thought some of you might find this interesting in light of recent issues
with SCO cc:
http://gcc.gnu.org/ml/gcc-patches/2003-08/msg00191.html
In short, the FSF is discussing the possibility of dropping support for SCO
Unix in GCC.
---(end of broadcast)--
Larry Rosenman <[EMAIL PROTECTED]> writes:
> cc -O -K inline -g -I../../../../src/include -I/usr/local/include -c -o
> printtup.o printtup.c
> UX:cc: WARNING: debugging and optimization mutually exclusive; -O disabled
> UX:acomp: ERROR: "printtup.c", line 94: undefined struct/union member:
> _sh
I think the new pg_get_triggerdef and pg_constraint_is_visible functions
aren't mentioned.
Chris
---(end of broadcast)---
TIP 7: don't forget to increase your free space map settings
No, the one where we always print hh:mm:ss for an interval, even if seconds
is zero.
--On Tuesday, August 05, 2003 01:03:57 -0400 Bruce Momjian
<[EMAIL PROTECTED]> wrote:
I don't know about that item. There is a menion of allowing 60 seconds
--- is that it?
--
On Sun, 10 Aug 2003, Vadim Mikheev wrote:
> FarewellIt's time for formal acknowledgement that I'm not in The Project any more.
>
> I'm not interested in small features/fixes and have no time for big ones.
> It was this way for very long time and I don't see how/when that could change.
>
> My part
I should have said "struct timezone' instead of 'struct tz' (ain't no
such animal). But the first argument is a struct timeval *, which has
no reference to a timezone.
Anyway - pointless to argue - I'll make the changes. NULL should work:
the man page says this:
If either tv or tz is nul
I forgot to update the typedefs for 7.4 before running pgindent. I
would like to run it again, hopefully soon. It shouldn't change very
much at all, but will recognize more of the typedefs.
OK?
--
Bruce Momjian| http://candle.pha.pa.us
[EMAIL PROTECTED]
On Mon, 2003-08-11 at 13:44, elein wrote:
> Yes, I actually have a libwsock32 because my
> system has wine on it. Wine is a windows
> emulator.
>
Wine Is Not an Emulator :-)
Robert Treat
--
PostgreSQL :: The Enterprise Open Source Database
---(end of broadcast)
Christopher Kings-Lynne writes:
> The most useful reason (and I wish you could turn it on with psql < file) is
> the line number in the file where any errors occur.
psql -f file will do that.
--
Peter Eisentraut [EMAIL PROTECTED]
---(end of broadcast)-
> My other question is we play around with bytea fields to escape nulls and
> chars < 32 and stuff so that when someone browses the table, they get
> '\000\000...', etc. However, are the other field types for which
> we have to do this? Can you put nulls and stuff in text/varchar/char
> fields?
Using the attached script, the build fails while trying ot tar up the
distributions ... when its trying to build the tools tar file, error being
that it can't find the src/data directory ... compared against the
snapshot build script, it doesn't look like I've missed anything, and i
haven't change
Seems to be OK. See below.
BTW, for those interested, following up a note from Joe Conway I
discovered yesterday the Right Way (tm) to build RPMs (nothing Pg
specific in this). Basically, you set up some rpm macros like this in
~/.rpmmacros:
%_topdir%(echo ${HOME}/rpm)
%_tmppath
following is taken from postgresql-7.3.2/src/backend/storage/lmgr/readme:
"If we are setting a table level lock
both the blockId and tupleId (in an item pointer this is called
the position) are set to invalid, if it is a page level lock the
blockId is valid, while the tuple
I propose that the following should be added to the TODO list:
- expose read-only NEW/OLD rowsets in statement-level triggers that
represent the affected rows.
- Implement a way to enable triggers to check which columns are affected
by the triggering statement.
Regards,
Andreas
-
Andi,
> Another way to specify a safe but efficient "TRUNCATE ALL" command that
> might be easier to implement than above "TRUNCATE table
> [CASCADE|RESTRICT]" might be to implement the functionality of the
> originally suggested "TRUNCATE ALL" through a psql meta-command. Any
> suggestions for a
On Tue, Aug 12, 2003 at 04:01:33PM -0400, Tom Lane wrote:
> Bruce Momjian <[EMAIL PROTECTED]> writes:
> > Can I have a TODO for this?
>
> * Prevent accidental re-use of sysids for dropped users and groups
>
> The other part of the thread was something like
>
> * Prevent dropping user that still
"Christopher Kings-Lynne" <[EMAIL PROTECTED]> writes:
> gcc -pipe -O -Wall -Wmissing-prototypes -Wmissing-declarations -Wno-error -I
> ./../include -I. -I../../../../src/include -DMAJOR_VERSION=3 -DMINOR_VERSIO
> N=0 -DPATCHLEVEL=0 -DINCLUDE_PATH=\"/home/chriskl/local/include\" -c -o
> preproc.o
I thought that statement level triggers did not work yet.
Are they supposed to work in 7.4?
(But even if they don't work they shouldn't crash...)
elein
On Sun, Aug 03, 2003 at 08:04:11PM -0700, Joe Conway wrote:
> I was working on trigger support for PL/R and ran across this bug in my
> own cod
On Mon, 2003-08-11 at 00:36, Vadim Mikheev wrote:
> It's time for formal acknowledgement that I'm not in The Project any
> more.
>
> I'm not interested in small features/fixes and have no time for big
> ones.
> It was this way for very long time and I don't see how/when that could
> change.
>
>
That line is certainly strange:
#0 0x40099ac5 in dllname () from /usr/lib/libwsock32.so
When you run configure, it says you are on Linux, right?
My guess is that gdb is getting confused because there is no dllopen
call in StreamServerPort().
---
> We could also think about providing an interface to do just Parse,
> although this is inessential since you can set up a prepared statement
> by PQexec'ing a PREPARE command.
Wait just a minute! phpPgAdmin would love to be able to 'parse' arbitrary
sql entered by the user to separate semi-colon
I don't think you see what I mean :)
I want to display the data on a webpage to the user. This means that a
varchar containing the string "I don't want it", should not appear as "I
don''t want it". So pg_escape_string isn't used there. bytea is different
tho because the default display isn't te
--On Friday, August 08, 2003 15:31:09 -0500 Larry Rosenman <[EMAIL PROTECTED]>
wrote:
The fix won't be out until Update Pack 3 at least (which is 3 months
away). It **MIGHT** make an update pack but I don't know.
I meant Maintenance Pack. The difference is the Update Packs cost a
subscriptio
Robert Creager <[EMAIL PROTECTED]> writes:
>> Could you supply the relation names corresponding to the relation OIDs
>> appearing in pg_locks, so we can be sure who's processing what?
> Sure, if you tell me how ;-) I looked at the view definition and that didn't help
> me much...
select relname
--On Tuesday, August 05, 2003 11:29:50 -0400 Tom Lane <[EMAIL PROTECTED]>
wrote:
Bruce Momjian <[EMAIL PROTECTED]> writes:
How is this?
Prevent timestamp from supressing ':00' seconds display
I think that was type interval, not timestamp.
Yeah, it is. (my bad, I think).
LER
regard
It occurred to me after I wrote that functions with 'security definer'
would present a problem with any default owner changing scheme. I like the
mass reassignment suggestion.
andrew
Chris wrote:
> Ah OK, I must have been thinking of the database owner check. I'd vote
> for (1) checking that th
Bruce,
> o Allow array declarations and other data types in PL/PgSQL DECLARE
> o Allow PL/PgSQL to support array element assignment
AFAIK, these two are not done, but they are redundant. Either one requires
the implementation of the other.
> o Add PL/PgSQL PROCEDURES th
The Hermit Hacker wrote:
> On Thu, 7 Aug 2003, Bruce Momjian wrote:
>
> > Tom Lane wrote:
> > > Bruce Momjian <[EMAIL PROTECTED]> writes:
> > > > I was just testing the threaded ecpg, and ran some performance tests.
> > > > Without using threads, I am seeing 100,000 inserts of a single word into
>
Tom Lane wrote:
Andreas Pflug <[EMAIL PROTECTED]> writes:
Only very-well-documented operators (Chapter 4.1.6) are parens-optimized
(+-*/%);
At the moment ... but you can be sure there will be demand to get smarter.
I never claimed to implement the ultimate solution, just wanted t
Can I have a TODO for this?
---
Tom Lane wrote:
> Gavin Sherry <[EMAIL PROTECTED]> writes:
> > On Tue, 12 Aug 2003, Andrew Dunstan wrote:
> >> Is this a security hole? Looks like one to me. Would it be better to use
> >> a
> But that's an additional feature, not a missing feature.
>
> I think the reason we are restrictive about the comparable cases for
> relations (pg_class entries) is that we use pg_class entries for a
> number of things that users see as unrelated or only weakly related.
> For example, indexes are
Hi all,
the following code was working properly under Postgres 7.3.X
I'm now running my regression test with Postgres 7.4beta1 and I'm
having the error in subj.
CREATE TABLE test ( a integer, b integer );
INSERT INTO test VALUES ( 1 );
CREATE OR REPLACE FUNCTION foo(INTEGER)
RETURNS INTEGER AS'
> No, but I wouldn't bet on DROP DOMAIN uniformly saying "domain" either.
> It's the same code as soon as you get below the top-level command
> routine (compare RemoveType and RemoveDomain).
>
> > I can't see any conceivable reason to allow this syntax to work!
> > We are giving zero benefit for a
101 - 200 of 353 matches
Mail list logo
