* Kristofer Munn <[EMAIL PROTECTED]> [001005 22:41] wrote:
> On Fri, 6 Oct 2000, Tom Lane wrote:
>
> > SIGSEGV, ie, bad pointer dereference. There should be a core dump
> > file --- can you provide a stack backtrace from it?
>
> I can try:
>
> # gdb bin/postgres core
> GNU gdb 4.17.0.11 with L
A good while back, Oleg Broytmann <[EMAIL PROTECTED]> wrote:
>> ran=> create table test1 (n int default nextval('seq_test'), t text);
>> ran=> insert into test1 ("t") select distinct src from test_source;
>> [ doesn't work right ]
> My, that's an interesting case. I think that fits right in with
On Fri, 6 Oct 2000, Tom Lane wrote:
> SIGSEGV, ie, bad pointer dereference. There should be a core dump
> file --- can you provide a stack backtrace from it?
I can try:
# gdb bin/postgres core
GNU gdb 4.17.0.11 with Linux support
Copyright 1998 Free Software Foundation, Inc.
GDB is free softwa
Kristofer Munn <[EMAIL PROTECTED]> writes:
> Anyone have any idea what status 139 is?
SIGSEGV, ie, bad pointer dereference. There should be a core dump
file --- can you provide a stack backtrace from it?
regards, tom lane
I got a message in my syslog stating:
Server process (pid 26969) exited with status 139 at Thu Oct 5 03:02:21
2000
It disconnected all other active processes, etc.
Anyone have any idea what status 139 is?
- K
Kristofer Munn * KMI * 732-254-9305 * AIM KrMunn * http://www.munn.com/
Quite awhile ago, Michael Richards <[EMAIL PROTECTED]> wrote:
> It looks like the order by is only being applied to the original select,
> not the unioned select. Some authority should check on it, but by thought
> it that a union does not necessarily maintain the order, so the entire
> select sho
At 12:05 6/10/00 +0900, Hiroshi Inoue wrote:
>
>Tom Lane wrote:
>
>> Hiroshi Inoue <[EMAIL PROTECTED]> writes:
>> P.S. I've noticed that get_rte_attribute_name() seems to
>> break my implementation. I'm not sure if I could solve it.
>> >>
>> >> That would be a problem --- rule dumping de
Tom Lane wrote:
> Hiroshi Inoue <[EMAIL PROTECTED]> writes:
> P.S. I've noticed that get_rte_attribute_name() seems to
> break my implementation. I'm not sure if I could solve it.
> >>
> >> That would be a problem --- rule dumping depends on that code to
> >> produce correct aliases, s
Hiroshi Inoue <[EMAIL PROTECTED]> writes:
P.S. I've noticed that get_rte_attribute_name() seems to
break my implementation. I'm not sure if I could solve it.
>>
>> That would be a problem --- rule dumping depends on that code to
>> produce correct aliases, so making it work is not optio
Try the attached patch against 7.0.2 --- not well tested but it
seems to work...
regards, tom lane
*** src/backend/executor/nodeMaterial.c.origWed Mar 1 23:06:39 2000
--- src/backend/executor/nodeMaterial.c Thu Oct 5 21:28:47 2000
***
*** 8,14
*
Brian Hirt <[EMAIL PROTECTED]> writes:
> I've run into a really strange problem that's taken a while for
> me to track down, but I think I have enough information here
> for people to verify what I'm saying and hopefully enough information
> to point someone in the right direction for fixing.
Na
Tom Lane wrote:
> "Hiroshi Inoue" <[EMAIL PROTECTED]> writes:
> > Seems some people expect the implementation in 7.1.
> > (recent [GENERAL} drop column?)
> > I could commit my local branch if people don't mind
> > backward incompatibility.
>
> I've lost track --- is this different from the _DROP
Hello,
I've run into a really strange problem that's taken a while for
me to track down, but I think I have enough information here
for people to verify what I'm saying and hopefully enough information
to point someone in the right direction for fixing.
My basic problem is that several queries
Peter Eisentraut <[EMAIL PROTECTED]> writes:
> Btw., something that has struck me as odd is that the hpux template with
> the native compiler sets CFLAGS='-Wl,-E -Ae'. I know what the -Ae is for,
> but the -Wl,-E should probably not be in every compilation command,
> no? (in particular since LDFL
Tom Lane writes:
> On HPUX, for example, the loader has to be given a -E switch when
> linking the postgres executable.
Btw., something that has struck me as odd is that the hpux template with
the native compiler sets CFLAGS='-Wl,-E -Ae'. I know what the -Ae is for,
but the -Wl,-E should probab
Frederick W. Reimer writes:
> This may sound stupid, but what's wrong with including a binary make
> executable in a binary PostgreSQL package?
We don't need "make" for the regression test.
--
Peter Eisentraut [EMAIL PROTECTED] http://yi.org/peter-e/
"Frederick W. Reimer" <[EMAIL PROTECTED]> writes:
> I'm getting the following error when I add a row to a table that has a
> trigger set for a plpgsql function. I did a nm on the plpgsql.so file and
> it lists CurrentMemoryContext as being in there, so I don't know why it
> can't find it.
> "DBD:
Oh, forgot to say that this is v7.0 on Solaris 7...
Fred
> -Original Message-
> From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On
> Behalf Of Frederick W. Reimer
> Sent: Thursday, October 05, 2000 3:21 PM
> To: [EMAIL PROTECTED]; [EMAIL PROTECTED]
> Subject: [PORTS] symbol not found i
"Hiroshi Inoue" <[EMAIL PROTECTED]> writes:
> Seems some people expect the implementation in 7.1.
> (recent [GENERAL} drop column?)
> I could commit my local branch if people don't mind
> backward incompatibility.
I've lost track --- is this different from the _DROP_COLUMN_HACK__
code that's alre
This may sound stupid, but what's wrong with including a binary make
executable in a binary PostgreSQL package? It could be stored in the
regression test directory and then you could write a "standard" regression
test makefile instead of a different "script" for each platform. A compiler
would b
I sent an email on this the other day, but didn't see it pop up in the list
and there have been no responses, so I don't know if it got through. Sorry
if this is a dup.
I'm getting the following error when I add a row to a table that has a
trigger set for a plpgsql function. I did a nm on the
> -Original Message-
> From: Tom Lane
>
> Bruce Momjian <[EMAIL PROTECTED]> writes:
> > OK, I am opening this can of worms again. I personally would like to
> > see this code activated, even if it does take 2x the disk space to alter
> > a column. Hiroshi had other ideas. Where did we le
Lamar Owen writes:
> That said, I have a request -- since the binary distributions might
> possibly be installed on machines with no make and no compiler, I would
> like to see the regression tests be reduced to a simple script and
> driver that could be simply invoked with no need for make. Bin
Hi,
Im still trying to figure out how postgre does things. And Im clueless.
Somewhere inside the backend there must occur a compare between "column" and
'string'. But where (and how)?
Ive been messing around with the source code in Linux, but with no success.
// Jarmo
PS. dbinit failed when I
Hi!
Where can I find the documentation of Postgres's compiler and optimizer?
who has anything about this subject?
Ricardo
[EMAIL PROTECTED]
November 1.
> Thus spake Bruce Momjian
> > I have installed this in the current source tree, ready for 7.1.
> >
> > I have installed >
> > > Announce: Release of PyGreSQL version 3.0
>
> When is 7.1 being locked down? I may be releasing 3.1 with a few small
> fixes and changes very soon.
>
>
[EMAIL PROTECTED] (D'Arcy J.M. Cain) writes:
> When is 7.1 being locked down? I may be releasing 3.1 with a few small
> fixes and changes very soon.
You've probably got about 2 weeks before beta starts. Bug fixes are
accepted during beta freeze, of course --- just no new-feature
development.
Probably [EMAIL PROTECTED] isnt work from my network :(
--
The reboots are for hardware upgrades!
"http://www.nmmm.nu"; < [EMAIL PROTECTED] >
-Original Message-
From: Nikolay Mijaylov [mailto:[EMAIL PROTECTED]]
Sent: Thursday
Thus spake Bruce Momjian
> I have installed this in the current source tree, ready for 7.1.
>
> I have installed >
> > Announce: Release of PyGreSQL version 3.0
When is 7.1 being locked down? I may be releasing 3.1 with a few small
fixes and changes very soon.
--
D'Arcy J.M. Cain| Democ
Matthew Hagerty wrote:
> Greetings,
>
> Well, it seems that the numeric issue I was having has nothing to do with
> the precision and scale being set the same, it has to do with the input
> data. The precision has to be at least 2 greater than the biggest number
> you need to enter, i.e.
>
> equi
30 matches
Mail list logo
