okay, then I'm doing it wrong ... I'm using -l "-r" ... 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 detai
Dear Sir.
Would you like to inform me how to modify type
in table?
For example , I define type as varchar(14) , but
I want to modify to varchar(120). How to do this.
Thank you so much
Jaruwan
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
B
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 rele
Kovacs Zoltan <[EMAIL PROTECTED]> writes:
> CREATE TABLE pakolas_cikktetel (
> pakolas int4 not null,
> cikk int4 not null,
> minoseg int4 not null,
> sorszam int4 check (sorszam > 0),
> helyrol int4,
> helyre int4,
> mennyi numeric(14,4) not null ,
> lezarva bool d
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 int
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 (
> * 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 th
* 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 <[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: 2001
* 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, Ga
LAZY VACUUM (Vadim)
Runtime btree recovery (Vadim)
JDBC setMaxRows() is global variable affecting other objects
JDBC LargeObject short read return value missing
ODBC not disconnecting properly?
Merge MySQL/PgSQL translation scripts
Fix ipcclean on Linux
unixODBC
--
Bruce Momjian
> 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 lurki
> 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, t
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 q
Jaruwan Laongmal wrote:
[Charset windows-874 unsupported, skipping...]
> Dear Sir,
>
> I will highly appreciated if anyone could inform me how to solve the following
>problems in Postgres.
> Specifically, sometimes there are the following messages informed by postgres.
>
> -
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
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
anyw
KuroiNeko wrote:
> > 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
Bruce Momjian wrote:
>
> I would LOVE to see it in a minor 7.1.X release.
It's *feature* with alot necessary coding in core
functionality below heap access methods. Not a good candidate
for a bugfix release.
Jan
>
>
> > Bruce,
> >
> > Thanks for replying (I know you're
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
> 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 tr
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 somethin
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 rel
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
> 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
I would LOVE to see it in a minor 7.1.X release.
> 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:
>
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 imp
> >> 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 u
> >Ok. I have made patches for fixing some of pg_dump problems(see
> >attached patches). The patches address the problem with user defined
> >functions, operators and aggregates.
>
> These have now been applied with minor modifications.
Thanks. BTW, are you going to make a back patch for the 7.
> 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 pr
> A compromise position would be to allow dropping trailing columns only
> when the column name list is omitted.
>
> Comments?
Sounds reasonable to me.
Andreas
> Vince Vielhaber <[EMAIL PROTECTED]> writes:
> > Shouldn't this insert fail? This is 7.0.3.
>
> > template1=# create table foo(x int,y varchar(10),z datetime);
> > CREATE
> > template1=# insert into foo(x,y,z) values(1,'asdf');
> > INSERT 19222 1
>
> We've always allowed trailing columns to b
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
> the new EXECUTE command in PL/pgSQL is a security hole.
This actually depends but I must admit that I'm concerned too. However,
the responsibility for the results should be split adequately IMHO. DBAs
should take care about unathorized access to PGSQL server, that's why
pg_hba.conf
Vince Vielhaber <[EMAIL PROTECTED]> writes:
> Shouldn't this insert fail? This is 7.0.3.
> template1=# create table foo(x int,y varchar(10),z datetime);
> CREATE
> template1=# insert into foo(x,y,z) values(1,'asdf');
> INSERT 19222 1
We've always allowed trailing columns to be omitted, whether
> Hi Bruce,
>
> Any idea when it's due for??
When? Probably not until 7.2, which is a pain.
--
Bruce Momjian| http://candle.pha.pa.us
[EMAIL PROTECTED] | (610) 853-3000
+ If your life is a hard drive, | 830 Blythe Avenue
+ Christ can be y
> 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 thinking of??
L
It is 3.1 already. The problem is that Announce says 3.1, while the
README says 2.5. I am CC'ing the author to update it.
> I got a bug report on the PyGreSQL version included with PostgreSQL 7.0.3:
>
> "version 3.1 pygresql is available and there's also a 3.2 beta. the
> packaged version is
Shouldn't this insert fail? This is 7.0.3.
template1=# create table foo(x int,y varchar(10),z datetime);
CREATE
template1=# insert into foo(x,y,z) values(1,'asdf');
INSERT 19222 1
template1=#
If not, why not? z's missing from the values(). Sybase fails it:
1> create table foo(x int,y varch
Tom Lane wrote:
> 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 r
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:
> ftp://ftp.postgresql.
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 f
"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
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 UNIX-useri
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
[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. I
On Sat, 27 Jan 2001, Tom Lane wrote:
> Oleg Bartunov <[EMAIL PROTECTED]> writes:
> > btw, is there way to specify default ops for index ?
>
> Sure, that's what pg_opclass is for. Just insert the opclass name
> and the OID of the type you want it to be the default index opclass
> for.
Tom, we al
Hi,
Beeing very impressed by TOAST, I wonder how I can insert BLOB from a flat
file.
It seems quite easy with php; But how can I do it from psql??
TIA
--
Olivier PRENANT Tel:+33-5-61-50-97-00 (Work)
Quartier d'Harraud Turrou +33-5-61-50-97-01 (Fax)
31190 AUTERIVE
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. Th
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 no
El Dom 28 Ene 2001 16:59, Olivier PRENANT escribió:
>
> Beeing very impressed by TOAST, I wonder how I can insert BLOB from a flat
> file.
>
> It seems quite easy with php; But how can I do it from psql??
I think you mean that it seems easy, because I haven't been able to
understand it (always t
Dear Sir,
I will highly appreciated if anyone could
inform me how to solve the following problems in Postgres.
Specifically, sometimes there are the following messages
informed by postgres.
NOTICE: Message from PostgreSQL
backend:
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 thinking of??
Regards,
On Sun,
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 this function except to implement 'modes' of
DES.', so you
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
> mor
56 matches
Mail list logo
