Matthew Hagerty <[EMAIL PROTECTED]> writes:
> 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.
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.
equinox=# create table test ( d numeri
Greetings,
I'm not sure if this is a bug, but I thought someone might like to know
about it. If you create a numeric field with the precision and scale set
the same, you can't insert anything into the field... pg-7.0.2 on
FreeBSD-4.0-Rel.
Matthew
equinox=# create table test2 ( d numeric(8
I wrote:
> My proposal is to set includedir=${prefix}/include/postgresql (instead of
> ${prefix}/include) in such cases where the prefix is shared, i.e., it does
> not contain something like "pgsql" already. (precise pattern t.b.d.)
I think that most people agreed to this step, or at least no
On Wed, Oct 04, 2000 at 11:49:30AM -0400, Tom Lane wrote:
> It looks to me like you ought to try to clean up the not-very-consistent
> treatment of constants in the grammar. Some rules use raw ICONST, some
> use Iconst, some use IntegerOnly --- ugh. There's no need for all that
> variation IMHO.
I have a problem with inheritance and references.
TABLE parent_table (
id_parent SERIAL PRIMARY KEY,
)
No primary key in child
TABLE child_parent (
.
) INHERITS (parent_table);
And another table :
TABLE other_table (
ref_child_table INTEGER REFERENCES parent_table
);
Reference must be
On Wed, 4 Oct 2000, Jan Wieck wrote:
> Stephan Szabo wrote:
> >
> > On Sun, 1 Oct 2000, Peter Eisentraut wrote:
> >
> > > Stephan Szabo writes:
> > >
> > > > With that, I do have a general question though. Are referential actions
> > > > supposed to be limited by the permissions of the user execu
Alfred Perlstein <[EMAIL PROTECTED]> writes:
> I have a reliable way to make postgresql crash after a
> couple of hours over here and a backtrace that looks like a good
> catch.
I'm interested in pursuing this, but the backtrace doesn't give enough
info to debug it. It looks like the backend is
Just a little question :
When I drop a database "xxx", and create another with the same name
"xxx", old database sequences are always.
Why ?
Olivier
Fabrice Scemama <[EMAIL PROTECTED]> writes:
> By the way, we finally understood that our main problem,
> the one that was making our Pg hang forever, comes from
> a deadlock problem. Same as Hannu's one.
> There are no deadlock detection, indeed. Good DBAs, or
> DBAs working with good coders, wil
[EMAIL PROTECTED] (D'Arcy J.M. Cain) writes:
> WaitOnLock: error on wakeup - Aborting this transaction
What happens to NOTICEs in your application?
For some odd reason, deadlock reports come out as a NOTICE followed by
this error message; if you are bit-bucketing NOTICEs then you may well
be con
Michael Meskes <[EMAIL PROTECTED]> writes:
> Anyway, the problem is that some rules expand to either Iconst, FCONST or
> Sconst. So do I have to change all these rules?
> Just changing the rule for Iconst and Sconst e.g doesn't work since
> AexprConst expands to the variable in two different way
A client just got this error. Anyone know why I suddenly get this?
The program has been working flawlessly for months before this.
WaitOnLock: error on wakeup - Aborting this transaction
--
D'Arcy J.M. Cain| Democracy is three wolves
http://www.druid.net/darcy/| and a she
"Vladimir V. Zolotych" <[EMAIL PROTECTED]> writes:
> my=> select days_in_month(3, 3, 3);
> ERROR: Can't find function days_in_month in file /tmp/days.so
Try using 'nm' to see what symbol name is actually being exported
from the .so file. I suspect that despite your use of extern "C",
your C+
Hello all,
I thought I would give it a try anyways...
This data type is based on Garrett A. Wollman isbn / issn code
It can be downloaded from:
ftp://ftp.freaky-namuh.com/pub/devel/Postgresql/version_number/version_number-0.2.tar.gz
The README file explains most of it.
It's not perfect, but
I would like to allow variables in ECPG at all positions the backend allows
constants. But I wonder how to get this done in the parser.
1) I need to allow :variable:indicator in AexprConst since this is the only
position where NULL is a possible constant.
2) :variable should be allowed whereever
Hannu Krosing <[EMAIL PROTECTED]> writes:
> I'm in a situation where I urgently need to debug PostgreSQL 7.0.2
> for deadlocks that it does not notice/timeout
The most likely bet is that you are seeing deadlocks that involve a
buffer spinlock (LockBuffer() in bufmgr.c) --- there's no timeout or
Stephan Szabo wrote:
>
> On Sun, 1 Oct 2000, Peter Eisentraut wrote:
>
> > Stephan Szabo writes:
> >
> > > With that, I do have a general question though. Are referential actions
> > > supposed to be limited by the permissions of the user executing the query?
> > > So, if you for example have writ
At 19:55 3/10/00 +0200, Peter Eisentraut wrote:
>I think that pg_dump should not quote identifiers that only contain
>lower-case letters and underscores. That will make it easier to move
>dumps to other database products, because PostgreSQL is off the spec in
>matters case folding in identifiers.
Hello all,
Please help me with
create function days_in_month(int4, int4, int4) returns int4
as '/tmp/days.so' language 'c';
Can I write this function days_in_month in C++ ?
I've did the following:
extern "C" {
int days_in_month(int year, int mo, int day);
}
extern "C" {
int days_in_month(in
On Mon, Oct 02, 2000 at 12:00:46PM -0400, Bruce Momjian wrote:
> I have committed this patch. It offers a speed up to ecpg.
Thanks. I haven't found the time to do it so far. But since I wanted to this
is good news. :-)
Michael
--
Michael Meskes
[EMAIL PROTECTED]
Go SF 49ers! Go Rhein Fire!
Use
I just wanted to repost this one more time in case developers didn't
catch it. I have a reliable way to make postgresql crash after a
couple of hours over here and a backtrace that looks like a good
catch.
My apologies if this one time to many, I won't be posting it again.
thanks for your time,
22 matches
Mail list logo
