Ross J. Reedstrom writes:
Hmm, multiple processors, and lots of IPC:
[snip]
Since it's just you and the sysadmin: any chance you could bring
the system up uniprocessor (I don't even know if this is _possible_
with Sun hardware, let alone how hard) and run the regressions some
more?
Dear Sir,
I will highly appreciated if anyone could
inform me how to solve the following problems in Postgres.
Specifically,sometimes thereare the following messages
informed by postgres.
NOTICE: Message from PostgreSQL
backend: The
El Lun 29 Ene 2001 07:57, Alexander Klimov escribi:
Hi.
I had the same problem and sent bug report to [EMAIL PROTECTED]
some time ago (20 Sep 2000), so, hopefully, they will fix it eventualy.
There is a workaround for it. The comment in ssl/include/openssl/des.h
said: `You should not use
On Mon, 29 Jan 2001, Martin A. Marques wrote:
El Lun 29 Ene 2001 07:57, Alexander Klimov escribió:
Hi.
I had the same problem and sent bug report to [EMAIL PROTECTED]
some time ago (20 Sep 2000), so, hopefully, they will fix it eventualy.
There is a workaround for it. The comment in
[EMAIL PROTECTED], [EMAIL PROTECTED] writes:
#define fprintf(file,fmt,msg) elog(FATAL, "%s", (msg))
Meaning no disrespect : yuck... IMHO this is asking for trouble
whenever someone decides to use another yacc.
This is flex, not yacc, and our lexer has been flex-only for a long
time. It's
Oleg Bartunov [EMAIL PROTECTED] writes:
gist__int_ops| 1007
gist__intbig_ops | 1007
we want gist__int_ops to be default index opclass.
If we delete gist__intbig_ops entry from opclass, then we couldn't use
gist__intbig_ops !
Put in gist__intbig_ops with zero for the
Damn,
the new EXECUTE command in PL/pgSQL is a security hole.
PL/pgSQL is a trusted procedural language, meaning that
regular users can write code in it. With the new EXECUTE
command, someone could read and write arbitrary files under
the postgres
"Robert B. Easter" [EMAIL PROTECTED] writes:
In scan.l, there is:
decimal (({digit}*\.{digit}+)|({digit}+\.{digit}*))
real
((({digit}*\.{digit}+)|({digit}+\.{digit}*)|({digit}+))([Ee][-+]?{digit}+))
Could this be simplified as:
decimal (({integer}?\.{integer})|({integer}\.{integer}?))
Jan Wieck [EMAIL PROTECTED] writes:
the new EXECUTE command in PL/pgSQL is a security hole.
PL/pgSQL is a trusted procedural language, meaning that
regular users can write code in it. With the new EXECUTE
command, someone could read and write arbitrary files
The Hermit Hacker [EMAIL PROTECTED] writes:
In order to reduce the size of the email sent to everyone, we have
included a Changelog file detailing all changes, that is viewable in the
ChangeLogs subdirectory. This file is available outside of the
distribution at:
On Fri, Jan 26, 2001 at 11:55:16PM -0500, Bruce Momjian wrote:
I said:
Yes, there are lots of systems that will clean /tmp --- and since the
lock file is an ordinary file (not a socket) pretty much any tmp-cleaner
is going to decide to remove it. I think that I had intended to insert
A compromise position would be to allow dropping trailing columns only
when the column name list is omitted.
Comments?
Sounds reasonable to me.
Andreas
Huh? This would only be true if all operations inside plpgsql are
executed as superuser, which they are not. Seems to me the existing
defense against non-superuser using COPY is sufficient.
Sorry if I missed the point, but if I got it right, Pl/Pgsql EXECUTE will
allow execution of any
Also I'm not quite sure "#arg" (stringification) is
portable enough in all platforms.)
The patch looks fine to me, but I have no idea how portable #arg is
Use the CppAsString macro from our c.h ... that's what it's for.
It's actually fairly unlikely that anyone still uses a
Zeugswetter Andreas SB [EMAIL PROTECTED] writes:
A compromise position would be to allow dropping trailing columns only
when the column name list is omitted.
Sounds reasonable to me.
IIRC, there's some interaction between this behavior and the way that
INSERT ... DEFAULT VALUES is
missing SQL features hereabouts also, such as being able to write
a DEFAULTed column explicitly:
INSERT ... VALUES('foo', DEFAULT, 42);
and being able to insert multiple explicit rows:
INSERT ... VALUES('foo', DEFAULT, 42), VALUES('bar', 99, 44);
I think we should deal with all
Tatsuo Ishii [EMAIL PROTECTED] writes:
Thanks. BTW, are you going to make a back patch for the 7.0.x tree?
I'm sure we are going to have lots of complaints from users who are
developing their own user defined functions and about to use pg_dump
to upgrade to 7.1 after it is officially
On Mon, 29 Jan 2001, KuroiNeko wrote:
Sorry if I missed the point, but if I got it right, Pl/Pgsql EXECUTE will
allow execution of any program via exec*() call? If so, this will allow any
(system) user to execute arbitrary code as postgres (system) user, right?
If so, how can something
a DEFAULTed column explicitly:
INSERT ... VALUES('foo', DEFAULT, 42);
and being able to insert multiple explicit rows:
INSERT ... VALUES('foo', DEFAULT, 42), VALUES('bar', 99, 44);
I think we should deal with all of these issues at once, which means
it's not something to try to
pgsql/docs/TODO.detail now is 1.1MB. I just removed 'subquery' which
shrunk it from 1.5MB. Comments?
--
Bruce Momjian| http://candle.pha.pa.us
[EMAIL PROTECTED] | (610) 853-3000
+ If your life is a hard drive, | 830 Blythe Avenue
+ Christ
Bruce Momjian wrote:
pgsql/docs/TODO.detail now is 1.1MB. I just removed 'subquery' which
shrunk it from 1.5MB. Comments?
Yow! Nice stuff in there, that is for sure. Of course, that's alot of
space. What to do? Remove all the unnecessary e-mail headers?
Signatures? etc? excessive
This is flex, not yacc, and our lexer has been flex-only for a long
time. It's possible that the hack would break in a future version
of flex, but I doubt it. What else is a lexer going to use fprintf
for?
Hmm, well of course you are right... (and I could use some sleep too
:-). OK, this
Being as I was sort of the person who got EXECUTE into plpgsql... I find
it odd that people think you can execute random shell commands.. AFAICS,
EXECUTE is used to execute SQL queries (for when you don't want to cache
the query plan?) ...
Got it. Thanks. Sorry for the hassle. Back lurking
* Bruce Momjian [EMAIL PROTECTED] [010129 14:03]:
Fix ipcclean on Linux
I believe Peter_E handled the above last week
--
Larry Rosenman http://www.lerctr.org/~ler
Phone: +1 972-414-9812 E-Mail: [EMAIL PROTECTED]
US Mail: 1905 Steamboat Springs Drive,
* Bruce Momjian [EMAIL PROTECTED] [010129 14:03]:
Fix ipcclean on Linux
I believe Peter_E handled the above last week
All I see is below, and the diff -c shows just the grep change.
---
revision 1.7
date:
* Bruce Momjian [EMAIL PROTECTED] [010129 14:40]:
* Bruce Momjian [EMAIL PROTECTED] [010129 14:03]:
Fix ipcclean on Linux
I believe Peter_E handled the above last week
All I see is below, and the diff -c shows just the grep change.
I thought that was all that was crabbed about?...
* Bruce Momjian [EMAIL PROTECTED] [010129 14:40]:
* Bruce Momjian [EMAIL PROTECTED] [010129 14:03]:
Fix ipcclean on Linux
I believe Peter_E handled the above last week
All I see is below, and the diff -c shows just the grep change.
I thought that was all that was crabbed
Bruce Momjian wrote:
Hi Bruce,
Any idea when it's due for??
When? Probably not until 7.2, which is a pain.
We cannot use TOAST as is for BLOB/CLOB storage with a binary
IO interface over fastpath.
The reason is that you cannot force a column to be moved off
anyway and
On Fri, 26 Jan 2001, [koi8-r] . wrote:
Good Day, Dear Karel Zak!
Please, forgive me for my bad english and if i do not right with your
day time.
my English is more poor :-)
You are right, it is (was?) in TODO and it will implemented - I hope -
in some next release (may be in
Bruce,
Thanks for replying (I know you're a busy man :)
Any chance to have it backported to 7.1 or maybe in contrib???
This is a feature w all gonna lack (with GiST...)
Regards,
On Mon, 29 Jan 2001, Bruce Momjian wrote:
Hi Bruce,
Any idea when it's due for??
I've been thining about
I cannot create a certain table in 7.1beta4. With 7.0.2 there was not any
problem.
--
CREATE TABLE pakolas_cikktetel (
pakolas int4 not null,
cikk int4 not null,
minoseg int4 not null,
sorszam int4 check
I have a function to transform text into a
pseudo-metaphone variable, take this
example:
cddbsql=# select song, metatext(song) from cdsongs
where metatext(song) like
metatext('born to run') limit 3 ;
song | metatext
-+--
Born To Run | brntorn
Born To Run | brntorn
Olivier PRENANT wrote:
Hi Bruce,
Any idea when it's due for??
I've been thining about writing a user function; But I'll get stuck with
permission as a user function is running under the "postgres" or whatever
user instead of the calling user.
Also, what kind of binary interface are you
okay, then I'm doing it wrong ... I'm using -l "-rtag" ... will revert
to using dates next time instead :(
On Mon, 29 Jan 2001, Tom Lane wrote:
The Hermit Hacker [EMAIL PROTECTED] writes:
In order to reduce the size of the email sent to everyone, we have
included a Changelog file
Hi, I ran the same code on 7.1beta 3 and it works... I don't have beta4
installed...
newdb=# CREATE TABLE pakolas_cikktetel (
newdb(# pakolas int4 not null,
newdb(# cikk int4 not null,
newdb(# minoseg int4 not null,
newdb(# sorszam int4 check (sorszam 0),
newdb(# helyrol
35 matches
Mail list logo
