Tom Lane wrote:
> Bruce Momjian <[EMAIL PROTECTED]> writes:
> >> Seems like a pretty serious (not to say fatal) objection to me. Surely
> >> you can fix that.
>
> > OK, suggestions. I know CommandCounterIncrement will not help. Should
> > I do more pfree'ing?
>
> No, retail pfree'ing is not a
Tom Lane wrote:
> Bruce Momjian <[EMAIL PROTECTED]> writes:
> > How about if we hard-wire template1 as being no-write to public
> > somewhere in the code, rather than in the db tables?
>
> Seems pretty icky :-(
>
> It occurs to me that maybe we don't need to worry. The main reason why
> we've o
Bruce Momjian <[EMAIL PROTECTED]> writes:
> How about if we hard-wire template1 as being no-write to public
> somewhere in the code, rather than in the db tables?
Seems pretty icky :-(
It occurs to me that maybe we don't need to worry. The main reason why
we've offered the advice "don't fill te
Bruce Momjian <[EMAIL PROTECTED]> writes:
>> Seems like a pretty serious (not to say fatal) objection to me. Surely
>> you can fix that.
> OK, suggestions. I know CommandCounterIncrement will not help. Should
> I do more pfree'ing?
No, retail pfree'ing is not a maintainable solution. I was t
Tom Lane wrote:
> Bruce Momjian <[EMAIL PROTECTED]> writes:
> > As part of createdb, the new database will have to have it's public
> > schema changed to world-writable.
>
> That ain't gonna happen, unfortunately. CREATE DATABASE runs in some
> database other than the target one, so it's essenti
Tom Lane wrote:
> Bruce Momjian <[EMAIL PROTECTED]> writes:
> > One change in this patch is that because analyze now runs in the outer
> > transaction, I can't clear the memory used to support each analyzed
> > relation. Not sure if this is an issue.
>
> Seems like a pretty serious (not to say f
Bruce Momjian <[EMAIL PROTECTED]> writes:
> One change in this patch is that because analyze now runs in the outer
> transaction, I can't clear the memory used to support each analyzed
> relation. Not sure if this is an issue.
Seems like a pretty serious (not to say fatal) objection to me. Sure
Bruce Momjian <[EMAIL PROTECTED]> writes:
> As part of createdb, the new database will have to have it's public
> schema changed to world-writable.
That ain't gonna happen, unfortunately. CREATE DATABASE runs in some
database other than the target one, so it's essentially impossible for
the newl
We've got an OSX machine set up now, however we haven't had time to look
into the problem yet.
Chris
> -Original Message-
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED]]On Behalf Of David Santinoli
> Sent: Tuesday, 11 June 2002 12:48 AM
> To: [EMAIL PROTECTED]
> Subject: [HACKERS]
Ron Snyder wrote:
> > As part of createdb, the new database will have to have it's public
> > schema changed to world-writable.
>
> I have to admit that much of the schema related discussion has been over my
> head, but I think what I understand you to be saying here is that the
> default would b
> As part of createdb, the new database will have to have it's public
> schema changed to world-writable.
I have to admit that much of the schema related discussion has been over my
head, but I think what I understand you to be saying here is that the
default would be to allow anybody to create t
Would you send over a context diff, diff -c?
---
Jack Bates wrote:
>
> Hello:
>
> I took a look at the SSL code in libpq/fe-misc.c and noticed what I
> think is a small problem. A patch is included at the bottom of thi
There was discussion of how template1's "public" schema should behave.
I think the only solution is to make template1's public schema writable
only by the super-user. This way, we can allow utility commands to
connect to template1, but they can't change anything or add their own
tables.
As part
> > How is SIMILAR TO different from ~ ?
> >From the part of Thomas's email you snipped:
>Implement SQL99 SIMILAR TO as a synonym for our existing operator "~".
> So the answer is "not at all"
Right. I'm not certain about the regex syntax defined by SQL99; I used
the syntax that we already ha
> TODO item marked as done:
> * -Add SIMILAR TO to allow character classes, 'pg_[a-c]%'
Darn. Will have to be more careful next time ;)
- Thomas
---(end of broadcast)---
TIP 4: Don't 'kill -9' the postmaster
Bruce Momjian wrote:
> Tom Lane wrote:
> > I tried to repeat this:
> >
> > regression=# begin;
> > BEGIN
> > regression=# create table foo (f1 int);
> > CREATE
> > regression=# insert into foo [ ... some data ... ]
> >
> > regression=# analyze foo;
> > ERROR: ANALYZE cannot run inside a BEGIN/E
Tom Lane wrote:
> I tried to repeat this:
>
> regression=# begin;
> BEGIN
> regression=# create table foo (f1 int);
> CREATE
> regression=# insert into foo [ ... some data ... ]
>
> regression=# analyze foo;
> ERROR: ANALYZE cannot run inside a BEGIN/END block
>
> This seems a tad silly; I can
Thomas Lockhart wrote:
> I've just committed changes which implement three SQL99 functions and
> operators. OVERLAY() allows substituting a string into another string,
> SIMILAR TO is an operator for pattern matching, and a new variant of
TODO item marked as done:
* -Add SIMILAR TO to al
On Tue, Jun 11, 2002 at 11:08:11AM -0700, Josh Berkus wrote:
> Thomas,
>
> > I've just committed changes which implement three SQL99 functions and
> > operators. OVERLAY() allows substituting a string into another string,
> > SIMILAR TO is an operator for pattern matching, and a new variant of
>
On Tue, 11 Jun 2002, Tom Lane wrote:
> Stephan Szabo <[EMAIL PROTECTED]> writes:
> > As a related side note. The other part of the original patch (the NOT
> > EXISTS in the upd/del no action trigger) was rejected. For match
> > full and match unspecified the same result can be reached by doing
> Hello together
>
> i've seen a lot of discussion about a native win32/OS2/BEOS port of
> PostgreSQL.
>
> During the last months i've ported PostgreSQL over to Novell NetWare
> and i've
> changed the code that I use pthreads instead of fork() now.
>
> I had a lot of work with the variables and cl
Thomas,
> I've just committed changes which implement three SQL99 functions and
> operators. OVERLAY() allows substituting a string into another string,
> SIMILAR TO is an operator for pattern matching, and a new variant of
> SUBSTRING() accepts a pattern to match.
Way cool! Thank you ... this
> Also, you neglected to add PLACING to the gram.y keyword category lists.
OK. I'm also tracking down what seems to be funny business in the regex
pattern caching logic, so will have a couple of things to fix sometime
soon.
- Thomas
---(end of broadcast)
> > I already said it. The to_char() is 'tm' struct interpreter and use
> > standard internal PG routines for interval to 'tm' conversion.
> The point is it should _not_ do that for interval.
I use the tm structure to hold this structured information. I *think*
that Karel's usage is just what i
I've just committed changes which implement three SQL99 functions and
operators. OVERLAY() allows substituting a string into another string,
SIMILAR TO is an operator for pattern matching, and a new variant of
SUBSTRING() accepts a pattern to match.
Regression tests have been augmented and pass.
> > fduch=> SELECT to_char('100days'::interval, '-MM-DD HH24:MI:SS');
> > -
> > -00-10 00:00:00
> I already said it. The to_char() is 'tm' struct interpreter and use
> standard internal PG routines for interval to 'tm' conversion. We can
> talk about why 100days is
Hello,
is there any news about the Mac OS X shutdown issue?
It was discussed in a few April-May/2002 messages with the Subject
"Mac OS X: system shutdown prevents checkpoint". In short, during a
regular system shutdown on Mac OS X the postmaster is not terminated
gracefully, leading to troubles
On Tue, Jun 11, 2002 at 09:36:39AM -0700, Josh Berkus wrote:
> Karel,
>
> > The to_interval() will have another (you wanted) behaviour.
>
> Please, please, please do not use to_interval for text formatting of
> intervals. It's very inconsistent with the naming of other conversion
> functio
Karel,
> The to_interval() will have another (you wanted) behaviour.
Please, please, please do not use to_interval for text formatting of
intervals. It's very inconsistent with the naming of other conversion
functions, and will confuse the heck out of a lot of users. As well as
messing u
Also, you neglected to add PLACING to the gram.y keyword category lists.
(Perhaps someone should whip up a cross-checking script to verify that
everything known to keywords.c is listed exactly once in those gram.y
lists.)
regards, tom lane
---(end
Thomas Lockhart <[EMAIL PROTECTED]> writes:
> I've just committed changes which implement three SQL99 functions and
> operators.
I'm getting
gcc -O1 -Wall -Wmissing-prototypes -Wmissing-declarations -g -I../../../../src/include
-c -o regexp.o regexp.c
regexp.c: In function `textregexsubstr':
also, remember that for the cost of a single CPU oracle license you can
build a crankin' postgresql server... memory and I/O are way more
important than CPU power btw.
---(end of broadcast)---
TIP 1: subscribe and unsubscribe commands go to [EMA
On Tue, 11 Jun 2002, Tom Lane wrote:
> There's fairly extensive help available from the list 'bot itself.
> Try sending a message with
> help
> help set
> to [EMAIL PROTECTED] (There are a bunch of other help topics
> but I'm guessing "set" is most likely the command you need.)
>
> A
On Mon, 10 Jun 2002, Dann Corbit wrote:
> If you are going to completely replace the data in a table, drop the
> table, create the table, and use the bulk copy interface.
Actually, that's a bad habit to get into. Views disappear, as do triggers
or constraints. Better to 'truncate table' or 'd
There's fairly extensive help available from the list 'bot itself.
Try sending a message with
help
help set
to [EMAIL PROTECTED] (There are a bunch of other help topics
but I'm guessing "set" is most likely the command you need.)
A low-tech solution would be to subscribe all your
On Tue, 11 Jun 2002, Thomas Lockhart wrote:
> OK, I *really* need to get my majordomo account fixed up to keep from
> stalling posts from my various accounts to the various lists.
>
> I think that I can enter some aliases etc to allow this; where do I find
> out how? Searching the -hackers archiv
OK, I *really* need to get my majordomo account fixed up to keep from
stalling posts from my various accounts to the various lists.
I think that I can enter some aliases etc to allow this; where do I find
out how? Searching the -hackers archives brought no joy since the
obvious keywords show up
Bradley Kieser <[EMAIL PROTECTED]> writes:
> If you double-alias a column in a query (yeah, stupid, I know, but I did
> it by mistake and others will too!), then the dreaded "fmgr_info:
> function : cache lookup failed" message is kicked out. For example:
> select * from company c, references
I've just committed changes which implement three SQL99 functions and
operators. OVERLAY() allows substituting a string into another string,
SIMILAR TO is an operator for pattern matching, and a new variant of
SUBSTRING() accepts a pattern to match.
Regression tests have been augmented and pass.
If you double-alias a column in a query (yeah, stupid, I know, but I did
it by mistake and others will too!), then the dreaded "fmgr_info:
function : cache lookup failed" message is kicked out. For example:
select * from company c, references r where r.company_id=c.company.id;
Note that c.co
On Tue, Jun 11, 2002 at 06:22:55AM -0700, Thomas Lockhart wrote:
> > > fduch=> SELECT to_char('100days'::interval, '-MM-DD HH24:MI:SS');
> > > -
> > > -00-10 00:00:00
> > I already said it. The to_char() is 'tm' struct interpreter and use
> > standard internal PG rou
Hello together
i've seen a lot of discussion about a native win32/OS2/BEOS port of
PostgreSQL.
During the last months i've ported PostgreSQL over to Novell NetWare
and i've
changed the code that I use pthreads instead of fork() now.
I had a lot of work with the variables and cleanup but mayor p
NunoACHenriques <[EMAIL PROTECTED]> writes:
> A different error today:
> [MemoryContextAlloc: invalid request size 4294967295]
This could be a variant of the same problem: instead of getting a zero
tuple length from the sort temp file, we're reading a -1 tuple length.
Still no way to tell i
Bruce, this error and the one in your earlier post are not indicative
of the bug, but rather of the connection failing - looking at the
created ecpgdebug file should confirm this.
I have since compiled 7.3 with the patch locally and cannot recreate
the bug (after messing around with the HBA cfg f
Lamar Owen wrote:
> On Monday 10 June 2002 04:11 pm, Tom Lane wrote:
> > I think our develop mode/beta mode pattern has done a great deal to
> > contribute to the stability of our releases. If we go over to the same
> > approach that everyone else uses, you can bet your last dollar that our
> > r
Bruce, after checking the libecpg source i'm fairly sure the problem
is due to the malloc buffer that the float is being sprintf'd into
being too small... It is always allocated 20 bytes but with a %.14g
printf specifier -6e-06 results in 20 characters:
-6.0e-06
and the NULL goes...
OK, I have reproduced the problem on my machine:
#$ ./a.out floattest
col1: -0.06
*!*!* Error -220: No such connection NULL in line 21.
Wow, how did that "A" get into the query string:
insert into tab1 ( col1 ) values ( -6.002122251e-06A )
Quite str
Hi!
A different error today:
[MemoryContextAlloc: invalid request size 4294967295]
This is a more often (twice a week) error and I don't understand
why?...
I'm verifying the machine: fsck (with bad blocks chk), ... but no
hardware problems untill now.
-
Bruce, the attached source reproduces this on 7.2, I don't have a
later version at hand to test if it's been fixed:
createdb floattest
echo "CREATE TABLE tab1(col1 FLOAT);" | psql floattest
ecpg insert-float.pgc
gcc insert-float.c -lecpg -lpq
./a.out floattest
results in:
col1: -0.06
On Tue, 2002-06-11 at 11:21, Karel Zak wrote:
> On Tue, Jun 11, 2002 at 11:16:13AM +0200, Hannu Krosing wrote:
> > On Tue, 2002-06-11 at 09:34, Karel Zak wrote:
>
> > > I think, we can keep this behaviour for to_char(), the good thing
> > > is that you can formatting interval to strings that se
Marc G. Fournier wrote:
> On Mon, 10 Jun 2002, Bruce Momjian wrote:
>
> > > 2. Once Branch created, any *partially implemented* features will get
> > >rip'd out of the -STABLE branch and only fixes to the existing, fully
> > >implement features will go in
> >
> > Now, that is an interesti
On Tue, 2002-06-11 at 11:31, Karel Zak wrote:
> On Tue, Jun 11, 2002 at 12:37:09PM +0400, Fduch the Pravking wrote:
>
> > And 'DD' is defined as in range 1..31...
> > What if I try to select '100 days'?
> >
> > fduch=> SELECT to_char('100days'::interval, '-MM-DD HH24:MI:SS');
> >to_
On Mon, 10 Jun 2002, Bruce Momjian wrote:
> > 2. Once Branch created, any *partially implemented* features will get
> >rip'd out of the -STABLE branch and only fixes to the existing, fully
> >implement features will go in
>
> Now, that is an interesting idea.
Ya, I thought it was when yo
On Tue, Jun 11, 2002 at 12:37:09PM +0400, Fduch the Pravking wrote:
> And 'DD' is defined as in range 1..31...
> What if I try to select '100 days'?
>
> fduch=> SELECT to_char('100days'::interval, '-MM-DD HH24:MI:SS');
>to_char
> -
> -00-10 00:00:00
I alre
On Mon, 10 Jun 2002, Tom Lane wrote:
> There is a downside to changing away from that approach. Bruce
> mentioned it but didn't really give it the prominence I think it
> deserves: beta mode encourages developers to work on testing, debugging,
> and oh yes documenting. Without that forced "non
On Tue, Jun 11, 2002 at 11:16:13AM +0200, Hannu Krosing wrote:
> On Tue, 2002-06-11 at 09:34, Karel Zak wrote:
> > I think, we can keep this behaviour for to_char(), the good thing
> > is that you can formatting interval to strings that seems like
> > standard time (15:10:33), etc.
>
> But in
On Tue, 2002-06-11 at 04:53, Bruce Momjian wrote:
> Tom Lane wrote:
> > Bruce Momjian <[EMAIL PROTECTED]> writes:
> > > Hannu Krosing wrote:
> > >> What about
> > >>
> > >> DELETE relation_expr FROM relation_expr [ , table_ref [ , ... ] ]
> > >> [ WHERE bool_expr ]
> > >>
> > >> or
> > >>
> > >
On Mon, Jun 10, 2002 at 03:43:34PM +0200, Karel Zak wrote:
> On Mon, Jun 10, 2002 at 04:26:47PM +0200, Hannu Krosing wr ote:
> > perhaps show them with the precision specified and keep data for bigger
> > units in biggest specified unit.
> >
> > to_char('2years 1min 4sec'::interval, 'MM SS'); ==>
On Tue, 2002-06-11 at 09:34, Karel Zak wrote:
> On Mon, Jun 10, 2002 at 07:18:44PM +0200, Hannu Krosing wrote:
>
> OK, I add to_interval() to may TODO (but it's unsure for 7.3).
>
> > hannu=# select to_char('33s 15h 10m 5months'::interval, '.MM.DD
> > HH24:MI:SS');
> >to_char
Do you know any attempts to write native OLE DB provider for PostgreSQL (it
would give broader support for VS Net). I would like to write such provider
and I want to know if sombody tried it before. Could somebody help me with
protocol issues (I have read Backend/Frontend Protocol and studied ODBC
Are you using crypt on the connection?
Unfortunately, crypt is not reentrant.
> -Original Message-
> From: David Ford [mailto:[EMAIL PROTECTED]]
> Sent: Monday, June 10, 2002 6:16 PM
> To: Dann Corbit
> Cc: vikas p verma; [EMAIL PROTECTED]
> Subject: Re: [HACKERS] PostGres Doubt
>
>
>
On Mon, Jun 10, 2002 at 07:18:44PM +0200, Hannu Krosing wrote:
OK, I add to_interval() to may TODO (but it's unsure for 7.3).
> hannu=# select to_char('33s 15h 10m 5months'::interval, '.MM.DD
> HH24:MI:SS');
>to_char
> -
> .05.00 15:10:33
> (1 row)
62 matches
Mail list logo
