After create function and trigger, when I update "fams" by delete entry in
table "indi" I get this message :
ERROR: fmgr_info: function 19968: cache lookup failed
Here is an SQL script that makes this happen:
--
create
> At 16:10 13/10/00 -0400, Bruce Momjian wrote:
> >
> >So, I am really saying that core doesn't do much. You non-core folks
> >aren't missing anything.
> >
>
> The issue here is transparency: doing the right thing as well as being seen
> to do the right thing.
>
> When someone devotes hours of
At 22:12 13/10/00 -0400, Bruce Momjian wrote:
>
>The majority of core discussions are closed because either we need to
>decide on a central direction for the project (release date)
These are the things that you should consider making more transparent.
>or we need
>to discuss something that woul
> At 22:12 13/10/00 -0400, Bruce Momjian wrote:
> >
> >The majority of core discussions are closed because either we need to
> >decide on a central direction for the project (release date)
>
> These are the things that you should consider making more transparent.
>
> >or we need
> >to discuss s
On Sat, 14 Oct 2000, Philip Warner wrote:
> The fear is that this may distort other priorities - hence why
> increased transparency in decision making is important. If Bruce, Tom
> & Jan make a design decision, then chances are it's going to be pretty
> good. The problem is it will/may be seen as
"Ross J. Reedstrom" <[EMAIL PROTECTED]> writes:
>> So, I am really saying that core doesn't do much. You non-core folks
>> aren't missing anything.
> Yeah, that's what you say in public ... There is no cabal!
It's true that very little goes on on the private core mailing list,
and we try to kee
> > At 22:12 13/10/00 -0400, Bruce Momjian wrote:
> > >
> > >The majority of core discussions are closed because either we need to
> > >decide on a central direction for the project (release date)
> >
> > These are the things that you should consider making more transparent.
> >
> > >or we need
> On Sat, 14 Oct 2000, Philip Warner wrote:
>
> > The fear is that this may distort other priorities - hence why
> > increased transparency in decision making is important. If Bruce, Tom
> > & Jan make a design decision, then chances are it's going to be pretty
> > good. The problem is it will/ma
> I think ideally our role is one of cat herders, as you put it ---
> making the kinds of decisions that a group of dozens or hundreds
> can't make effectively. But the long-term direction of the project
> is largely determined by what the individual CVS committers choose to
> work on. In that s
At 16:53 13/10/00 -0200, Vilson farias wrote:
>Hi.
>
>I started testing pg_dump and I have a little question :
>
>What does pg_dump with data arrived while its running?
>
pg_dump runs in a single transaction, so in theory it dumps a consistent
view of the data, not necessarily the absolute latest
We have recently developed an interface to PostgreSQL for Matlab.
The interface is implemented as 'C' mex wrappers around libpq. Most of the
database connection and query execution functions are implemented, and it
supports default (text) and binary transfers directly into Matlab variables
(incl
On Fri, 13 Oct 2000, Darrin Rothe wrote:
> We have recently developed an interface to PostgreSQL for Matlab.
>
> The interface is implemented as 'C' mex wrappers around libpq. Most of the
> database connection and query execution functions are implemented, and it
> supports default (text) and b
Licensing shouldn't be an issue. I have permission from the university to
release it into "the public domain." However, I intend to attach the BSD
style license/disclaimer which exists with PostgreSQL. Matlab's license
does not impose any restrictions on programs written using their API.
Howeve
"Mitch Vincent" <[EMAIL PROTECTED]> writes:
> Well, all you're doing with pg_dump is getting a snapshot of the database at
> a single point in time -- as pg_dump reads the data out of the tables, I'm
> sure that it won't go back and re-read tables that have changed since it was
> first started. On
On Sat, 14 Oct 2000, Tom Lane wrote:
> I've just finished putting together a talk about MVCC transaction
> processing --- both how it behaves and how it's implemented --- for
> the upcoming OSDN database conference. I think the slides for that
> talk are fairly self-contained and might be of gen
"Tamsin" <[EMAIL PROTECTED]> writes:
> I want to remove a not null constraint from a table. I've read the posts
> about having to rename, recreate without not nulls & insert back into the
> table. This is fine, but the table also has a lot of foreign keys/rules etc
> & recreating all these is a
On Fri, 13 Oct 2000, Darrin Rothe wrote:
> Licensing shouldn't be an issue. I have permission from the university to
> release it into "the public domain." However, I intend to attach the BSD
> style license/disclaimer which exists with PostgreSQL. Matlab's license
> does not impose any restri
Michael Engelhart <[EMAIL PROTECTED]> writes:
> Thanks Adam. Yeah, I know that it uses a mach kernel and variant of
> freebsd runs atop the kernel. I would attempt the FreeBSD template
> but the other snag is that it has to compile on PowerPC.
FreeBSD template seems like it'd be a good starting
Dustin Sallings <[EMAIL PROTECTED]> writes:
> I'm quite sure ``vacuum analyze'' does both.
Correct.
> Is there a reason there's no ``analyze?''
Historical, mostly. No essential reason I can think of. In current
sources the "analyze" part is run as a separate read-only transaction
after
At 00:10 14/10/00 -0400, Tom Lane wrote:
>I think the slides for that
>talk are fairly self-contained and might be of general interest;
>shall I brace Vince about putting them up on the website?
This would be good to see. Would it fit in the documentation hierarchy
somewhere?
--
At 00:26 14/10/00 -0400, Tom Lane wrote:
>> I tried updating pg_attribute & setting attnotnull to 'f' for the field in
>> question. This seems to have worked. Is it safe?! - is there anything
else
>> I should be aware of?
>
>Yup, that should do the trick. Not much magic here...
>
Just to confi
"Darrin Rothe" <[EMAIL PROTECTED]> writes:
> We have recently developed an interface to PostgreSQL for Matlab.
> ...
> We would like to make this interface freely available, and would like to
> know how much interest there would be in the interface. Also, would it be
> worthwhile to package and m
Thanks to everyone for giving me a starting point.
here's what I tried so far:
changed the CFLAGS in the src/template/freebsd file to:
CFLAGS='-O0 -pipe'
did
./configure --with-template=freebsd
configure succeeded.
Did a make and started to build. During the build, there were a ton of messag
Philip Warner <[EMAIL PROTECTED]> writes:
> At 00:26 14/10/00 -0400, Tom Lane wrote:
>>> I tried updating pg_attribute & setting attnotnull to 'f' for the field in
>>> question. This seems to have worked. Is it safe?! - is there anything
>>> else I should be aware of?
>>
>> Yup, that should do
24 matches
Mail list logo
