Bruce Momjian <[EMAIL PROTECTED]> writes:
> The problem is that the more complex you make things, the easier it is
> to make a mistake. That's why I like our simpler model unless there is
> a glaring problem with it.
I think Bruno's got a good point. The implementation would be kind of
painful,
The problem is that the more complex you make things, the easier it is
to make a mistake. That's why I like our simpler model unless there is
a glaring problem with it.
---
Bruno Wolff III wrote:
> On Fri, Nov 01, 2002 at 2
On Fri, Nov 01, 2002 at 21:35:40 -0500,
Bruce Momjian <[EMAIL PROTECTED]> wrote:
>
> I think we open up more security problems by having the inserter doing
> things as the owner of the table.
With triggers it is a bit hard to decide. Since people other than the
table owner can create them, but
On Friday 01 November 2002 03:25 am, Jinqiang Han wrote:
> Hello,all.
> I have downloaded the 7.3.2 rpm. I use rpm -i to install the rpm.
> When I want to regenerate a new 7.3.2 rpm, I use 'rpm -ba
> postgresql-7.3.2.specs' in /usr/src/redhat/SPECS. It show errors. It seem
> perl5 don't exist in th
Added to TODO.
---
Tom Lane wrote:
> Bruce Momjian <[EMAIL PROTECTED]> writes:
> > Is this a TODO?
>
> Yes. Maybe
>
> * Acquire lock on a relation before building a relcache entry for it
>
> I'm not quite sure yet how th
Tom Lane wrote:
> Bruce Momjian <[EMAIL PROTECTED]> writes:
> > Tom Lane wrote:
> >> Do not hack up PerformPortalFetch; put the special case for INT_MAX in
> >> utility.c's FetchStmt code, instead. As-is, you probably broke other
> >> callers of PerformPortalFetch.
>
> > I thought about that, but
Tom Lane wrote:
> We could dike out the feature:
>
> convert_list:
> a_expr USING any_name
> {
> elog(ERROR, "CONVERT(... USING ...) is not implemented");
> }
>
> Short of that, I think we need an initdb to change the function
> sign
Larry Rosenman wrote:
> > We have always allowed old clients to connect to new servers, but often
> > break new servers connecting to old clients. I think this is documented
> > somewhere, but it rarely comes up as an issue.
> So, what do we do in this case, where an OLDER client (<=7.2.3) connect
> > We have always allowed old clients to connect to new servers, but often
> > break new servers connecting to old clients. I think this is documented
> > somewhere, but it rarely comes up as an issue.
> So, what do we do in this case, where an OLDER client (<=7.2.3) connects
> to a new (>=7.3)
Bruce Momjian <[EMAIL PROTECTED]> writes:
> Tom Lane wrote:
>> Unfortunately, I don't see any way offhand to fix this without an
>> initdb :-(.
> Ooch, that hurts. How bad would it be if it was broken in 7.3?
We could dike out the feature:
convert_list:
a_expr USING any_name
On Fri, 2002-11-01 at 21:54, Bruce Momjian wrote:
> Rod Taylor wrote:
> > On Fri, 2002-11-01 at 14:18, Larry Rosenman wrote:
> > > On Fri, 2002-11-01 at 12:25, Rod Taylor wrote:
> > > > > I know this, the question is, Should this happen? If not, can we fix it
> > > > > somehow?
> > > > >
> > > >
Tom Lane wrote:
> I have just noticed that the implementation of
> CONVERT(text USING encoding_name)
> tries to do database access during the grammar phase, viz it looks
> up the encoding_name in pg_conversion and replaces it with an OID.
>
> This is not workable; consider the situation wher
Tom Lane wrote:
> "Ulrich Neumann" <[EMAIL PROTECTED]> writes:
> > - 3 of the 8 mentioned sourcefiles are files that are heavily changed
> > for NetWare and I don't want to change the original files in this
> > case. I think it's better to have a copy of these files in the NetWare
> > folder. This
Rod Taylor wrote:
> On Fri, 2002-11-01 at 14:18, Larry Rosenman wrote:
> > On Fri, 2002-11-01 at 12:25, Rod Taylor wrote:
> > > > I know this, the question is, Should this happen? If not, can we fix it
> > > > somehow?
> > > >
> > > > Or do we need to put a note somewhere?
> > >
> > > I think
Is this a TODO?
---
Tom Lane wrote:
> Rod Taylor <[EMAIL PROTECTED]> writes:
> > ERROR: RelationClearRelation: relation 11584078 deleted while still in
> > use
>
> > I've been unable to come up with a test case that will
Tom Lane wrote:
> I am thinking it would be useful for debugging if elog(PANIC) were to
> exit by calling abort() so that a core dump would be produced.
>
> Going out via proc_exit(), as it now does, seems like a bad idea in any
> case, since that will try to do a bunch of cleanup activity that's
Tom Lane wrote:
> Bruce Momjian <[EMAIL PROTECTED]> writes:
> > The following patch makes FETCH/MOVE 0 do nothing, and FETCH LAST move
> > to the end.
>
> Do not hack up PerformPortalFetch; put the special case for INT_MAX in
> utility.c's FetchStmt code, instead. As-is, you probably broke other
I think we open up more security problems by having the inserter doing
things as the owner of the table.
---
Bruno Wolff III wrote:
> On Wed, Oct 30, 2002 at 14:03:21 -0600,
> >
> > While I am not sure about triggers, it ce
I have just noticed that the implementation of
CONVERT(text USING encoding_name)
tries to do database access during the grammar phase, viz it looks
up the encoding_name in pg_conversion and replaces it with an OID.
This is not workable; consider the situation where we are in an
already-abo
Andrew Sullivan wrote:
>
> On Wed, Oct 30, 2002 at 10:18:47AM -0500, Robert Treat wrote:
> > regarding replication, as well as a "high availability how-to" that
> > would probably be worth reading.
>
> The high availability howto suggests using rsync to synchronise the
> data areas of two data se
Ports list for Unixware 7.2 updated:
http://candle.pha.pa.us/main/writings/pgsql/sgml/supported-platforms.html
---
Olivier PRENANT wrote:
> I'm glad to tell that I compiled and run regression tests ok on unixware
> 711 and
AS strings are labels, not columns that can be referenced in a where
clause:
test=> select lanname as xx from pg_language where xx = 'yy';
Hannu is correct that making a FROM entry works.
---
Hannu Krosing wrote:
>
Peter Eisentraut <[EMAIL PROTECTED]> writes:
> I think the problem is more accurately described thus: Flex generated
> files include before "postgres.h" due to the way it lays out the
> code in the output. stdio.h does something which prevents switching to
> the large file model later on in post
7.3beta has much more powerful stored procedures. Basically, you can
put function names in the FROM clause of a SELECT. I recommend you try
that and then let us know exactly what is failing with Crystal Reports.
It may be just a syntax issue, or something more major.
---
Tommi Maekitalo wrote:
> Hi,
>
> I just installed 7.3b3 on my server (SuSE linux 8.1 on x86 with gcc 3.2) and
> discovered a problem with tabcompletition in pgsql. It doesn't work with
> schema. I created a schema 's' and a table 'tab' in this schema. When typing
> 'select * from s.' followed b
Here is an O'Reilly article talking about Oracle's OO capabilities:
http://www.oreillynet.com/pub/a/network/2002/10/29/Feuerstein.html
---
Hannu Krosing wrote:
> Karel Zak kirjutas K, 30.10.2002 kell 10:08:
> >
> >
At 4:31 PM -0500 11/1/02, Tom Lane wrote:
>Peter Bierman <[EMAIL PROTECTED]> writes:
>> At 1:30 AM -0500 11/1/02, Tom Lane wrote:
>>> Is it worth carrying two expected files for OS X 10.1 and 10.2? I'm
>>> inclined to think not, and am leaning towards updating the expected
>>> file. Comments?
>
>
Have you read the SCO FAQ?
http://www.us.postgresql.org/users-lounge/docs/faq.html
Also, we are about to release 7.3. Would you please try 7.3beta3 and
let us know how that works?
---
Shibashish wrote:
> Dear Sir,
Ugh. Path problem...sorry for jumping the gun.
On Fri, 1 Nov 2002, Laurette Cisneros wrote:
> 7.3b3
>
> as postgres user
>
> createuser laurette
> Shall the new user be allowed to create databases? (y/n) y
> Shall the new user be allowed to create more new users? (y/n) y
> ERROR: 'autocommi
Peter Bierman <[EMAIL PROTECTED]> writes:
> At 1:30 AM -0500 11/1/02, Tom Lane wrote:
>> Is it worth carrying two expected files for OS X 10.1 and 10.2? I'm
>> inclined to think not, and am leaning towards updating the expected
>> file. Comments?
> I'm 90% certain that the difference is caused b
7.3b3
as postgres user
createuser laurette
Shall the new user be allowed to create databases? (y/n) y
Shall the new user be allowed to create more new users? (y/n) y
ERROR: 'autocommit' is not a valid option name
createuser: creation of user "laurette" failed
any ideas?
Thanks,
--
Laurett
At 1:30 AM -0500 11/1/02, Tom Lane wrote:
>I said:
>> Peter Bierman <[EMAIL PROTECTED]> writes:
>>> Perhaps the change from gcc2.x to 3.x changed floats a bit?
>
>> Could be. We had previous reports of the same diff on OSX 10.2 with
>> a G4 processor, so I was wondering if it was hardware or softw
Barry Lind <[EMAIL PROTECTED]> forwards:
> If we had to supply gcj along with PostgreSQL in order for PostgreSQL to
> work, I guess that would mean gcj was incorporated in PostgreSQL - that
> would mean PostgreSQL would become subject to GPL protection.
Depends on how you define "work". pljava wo
Barry Lind <[EMAIL PROTECTED]> writes:
> If we had to supply gcj along with PostgreSQL in order for PostgreSQL to
> work, I guess that would mean gcj was incorporated in PostgreSQL - that
> would mean PostgreSQL would become subject to GPL protection.
Not true--"mere aggregation" (shipping two th
On Fri, 2002-11-01 at 14:18, Larry Rosenman wrote:
> On Fri, 2002-11-01 at 12:25, Rod Taylor wrote:
> > > I know this, the question is, Should this happen? If not, can we fix it
> > > somehow?
> > >
> > > Or do we need to put a note somewhere?
> >
> > I think it's a little late to fix now.
> >
Forwarding to hackers a discussion that has been happening off list.
--Barry
Original Message
Subject: Re: [HACKERS] PG functions in Java: maybe use gcj?
Date: 01 Nov 2002 19:13:39 +
From: Oliver Elphick <[EMAIL PROTECTED]>
To: Barry Lind <[EMAIL PROTECTED]>
References: <[EM
On Fri, 2002-11-01 at 12:25, Rod Taylor wrote:
> > I know this, the question is, Should this happen? If not, can we fix it
> > somehow?
> >
> > Or do we need to put a note somewhere?
>
> I think it's a little late to fix now.
>
> Making psql support multiple versions was a suggestion Tom made
> I know this, the question is, Should this happen? If not, can we fix it
> somehow?
>
> Or do we need to put a note somewhere?
I think it's a little late to fix now.
Making psql support multiple versions was a suggestion Tom made a while
back, but nobody took up the challenge.
--
Rod Ta
Tom,
I undestand that you think that it might be a nightmare. The idea
behind this idea is that NetWare doesn't use fork() to create a
process, it uses procle() or procve(). That's very similar to
NT's createProcess() or the combination of fork/exec.
Additional i've implemented a way that is base
"Ulrich Neumann" <[EMAIL PROTECTED]> writes:
> - 3 of the 8 mentioned sourcefiles are files that are heavily changed
> for NetWare and I don't want to change the original files in this
> case. I think it's better to have a copy of these files in the NetWare
> folder. This gives me the chance to use
On Fri, 2002-11-01 at 10:43, Tom Lane wrote:
> Larry Rosenman <[EMAIL PROTECTED]> writes:
> > Is the following supposed to work?
>
> No. 7.3 psql uses schema syntax in its internal queries, so it will
> fail to detect superuser status on pre-7.3 backends. Most backslash
> commands won't work ve
Hello together,
after some discussions with you and other people I want to add all
changes and additions that i've done with PostgreSQL back to you.
In order to do this I thought of the following way:
(If someone can comment on these ideas this would be great.)
- I've created a folder pgsql/src/N
Larry Rosenman <[EMAIL PROTECTED]> writes:
> Is the following supposed to work?
No. 7.3 psql uses schema syntax in its internal queries, so it will
fail to detect superuser status on pre-7.3 backends. Most backslash
commands won't work very well either :-(. However, manually issued
SQL should
On Fri, 2002-11-01 at 10:38, Rod Taylor wrote:
> On Fri, 2002-11-01 at 11:30, Larry Rosenman wrote:
> > Is the following supposed to work?
> >
> > $ psql -U neteng -h tide netmaster
> > ERROR: parser: parse error at or near "."
>
> 7.3 psql is schema safe.
>
> So... it's trying to do silly th
On Fri, 2002-11-01 at 11:30, Larry Rosenman wrote:
> Is the following supposed to work?
>
> $ psql -U neteng -h tide netmaster
> ERROR: parser: parse error at or near "."
7.3 psql is schema safe.
So... it's trying to do silly things like:
SELECT * FROM pg_catalog.pg_class;
Of course, 7.2 and
Larry Rosenman <[EMAIL PROTECTED]> writes:
> On Fri, 2002-11-01 at 09:53, Tom Lane wrote:
>> Or at least it's *trying* to apply it for 4.7 --- as near as I can tell
>> without testing, the above scrap of resultmap code is wrong because both
>> of the i.86 lines will match on FreeBSD 4.7, and I thin
Is the following supposed to work?
$ psql -U neteng -h tide netmaster
ERROR: parser: parse error at or near "."
Welcome to psql 7.3b3, the PostgreSQL interactive terminal.
Type: \copyright for distribution terms
\h for help with SQL commands
\? for help on internal slash command
On Fri, 2002-11-01 at 09:53, Tom Lane wrote:
> Sean Chittenden <[EMAIL PROTECTED]> writes:
> > $ uname -a
> > FreeBSD avienda.nxad.com 5.0-CURRENT FreeBSD 5.0-CURRENT #1: Mon Oct 28 18:20:14
>PST 2002 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/DELLAPTOP i386
>
> > Looks like the only problem on
Andrew Sullivan <[EMAIL PROTECTED]> writes:
> On Fri, Nov 01, 2002 at 09:38:31AM +0100, Mario Weilguni wrote:
>> I found a message I've never seen before in VACUUM, its:
>> NOTICE: Too old parent tuple found - can't continue repair_frag
>>
>> The version is Postgresql 7.2.1.
> I thought this was
Sean Chittenden <[EMAIL PROTECTED]> writes:
> $ uname -a
> FreeBSD avienda.nxad.com 5.0-CURRENT FreeBSD 5.0-CURRENT #1: Mon Oct 28 18:20:14 PST
>2002 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/DELLAPTOP i386
> Looks like the only problem on beta3 is that the geometry bits are
> failing, but I'm
Mario Weilguni <[EMAIL PROTECTED]> writes:
> I found a message I've never seen before in VACUUM, its:
> NOTICE: Too old parent tuple found - can't continue repair_frag
> This sounds like a solution should be available, but it seems to
> happen anyway. Yesterday I've found no way to fix this probl
On Fri, Nov 01, 2002 at 09:38:31AM +0100, Mario Weilguni wrote:
> I found a message I've never seen before in VACUUM, its:
> NOTICE: Too old parent tuple found - can't continue repair_frag
>
> The version is Postgresql 7.2.1.
I thought this was fixed in 7.2.2 or 7.2.3?
A
--
Andrew Sulliva
I said:
> The alter_table diff is clearly indicative of a bug. Can you set a
> breakpoint and discover exactly where calloc is blowing up?
Never mind, I see it: psql is doing calloc(0) when presented with a
table of zero columns. Surprising you're the first to try it on a
platform where that ret
Alessio Bragadini <[EMAIL PROTECTED]> writes:
> On Thu, 2002-10-31 at 18:53, Tom Lane wrote:
>> Evidently main.c needs "#include " added.
> I wonder what have changed since Beta2 that compiled fine...
That is odd. main.c itself certainly has not changed.
> Done, and now it builds (I've limited
On Thu, 2002-10-31 at 18:27, Barry Lind wrote:
> However in the proposal here we are talking about requiring a specific
> jvm (gcj) and actually linking parts of it into postgres. To the extent
> that GPL code is linked in the GPL extends to the entire code base. As
> I said previously there
On Fri, 2002-11-01 at 01:57, Sean Chittenden wrote:
> > > >>Seems like someone ought to issue a call for port reports. The
> > > >>"supported platforms" list hasn't been touched ...
> > > > Good point. Thomas, can you take that on?
> > >
> > > No, at least not now. I'm not able to communicate re
On Thu, 2002-10-31 at 18:53, Tom Lane wrote:
> Evidently main.c needs "#include " added.
I wonder what have changed since Beta2 that compiled fine...
> Please add that and see if you get any further.
Done, and now it builds (I've limited the test to native cc compiler for
now). But it doesn't
Hello,all.
I have downloaded the 7.3.2 rpm. I use rpm -i to install the rpm.
When I want to regenerate a new 7.3.2 rpm, I use 'rpm -ba postgresql-7.3.2.specs' in
/usr/src/redhat/SPECS. It show errors. It seem perl5 don't exist in the
/postgresql7.3.2-root/usr/bin/lib/.
After that I change the
58 matches
Mail list logo
