On Oct 22, 2008, at 1:43 PM, Andrew Dunstan wrote:
+ if (!CALLED_AS_TRIGGER(fcinfo))
+ elog(ERROR, "min_update_trigger: not called by trigger
manager");
The error I get in 8.2 when calling a trigger function directly is:
ERROR: trigger functions may only be called as triggers
T
On Oct 23, 2008, at 11:16 AM, Tom Lane wrote:
Gregory Stark <[EMAIL PROTECTED]> writes:
Tom Lane <[EMAIL PROTECTED]> writes:
Works fine for me, eg
I think he's looking for something like:
5 IN (col1,col2,col3)
resulting in a bitmap or of three index scans of three different
indexes on
co
Decibel! <[EMAIL PROTECTED]> writes:
> ... I would argue that rowvar_b IS NOT NULL should be false and rowvar_a
> IS NOT NULL should be true.
While I don't necessarily disagree with you about what is sane, what
is required by the SQL spec seems pretty clear here.
regards
On Oct 24, 2008, at 7:19 PM, Tom Lane wrote:
Decibel! <[EMAIL PROTECTED]> writes:
Was anything ever done with http://archives.postgresql.org/pgsql-
hackers/2008-09/msg01758.php ?
No, we got stalled on what the behavior really ought to be:
http://archives.postgresql.org/pgsql-hackers/2008-09/ms
[Re-sending to hackers, since the original message to pgsql-bugs has
not been approved for delivery in the last four days…apologies for any
duplicates.]
Howdy,
I ran into this error on 8.2 a while ago, and just figured out what
was causing it. Here's a quick example on 8.2:
BEGIN;
-- Co
"Tim Keitt" <[EMAIL PROTECTED]> writes:
> The docs for FETCH indicate you can fetch from the current row using
> FORWARD 0, but
> SPI_scroll_cursor_fetch(someportal, FETCH_FORWARD, 0);
> fails for me. Is there a way to emulate FETCH FORWARD 0 with SPI?
Fails how? AFAICS that calls the same
Decibel! <[EMAIL PROTECTED]> writes:
> Was anything ever done with
> http://archives.postgresql.org/pgsql-hackers/2008-09/msg01758.php ?
No, we got stalled on what the behavior really ought to be:
http://archives.postgresql.org/pgsql-hackers/2008-09/msg01772.php
> I have a different issue I'm se
Guillaume Lelarge <[EMAIL PROTECTED]> writes:
> So, it seems to work. I say "seems" because there's no XLOG record that
> says I moved all relations from one tablespace to another. Am I right in
> thinking I need to insert a new XLOG record? should I create a new one?
You certainly need to do *som
Was anything ever done with http://archives.postgresql.org/pgsql-
hackers/2008-09/msg01758.php ?
I have a different issue I'm seeing, but I think it's related, and
ISTM it's a bug (on 8.2.10):
SELECT INTO v_prev *
FROM installments_static
WHERE id = (S
Tom Lane a écrit :
> Guillaume Lelarge <[EMAIL PROTECTED]> writes:
>> To get the list of relations to move, the user needs to be connected to
>> the database.
>
> Why? If what you are doing is changing the database's default
> tablespace (which IMHO is what such a command ought to do)
That's exa
The docs for FETCH indicate you can fetch from the current row using
FORWARD 0, but
SPI_scroll_cursor_fetch(someportal, FETCH_FORWARD, 0);
fails for me. Is there a way to emulate FETCH FORWARD 0 with SPI?
Also, I noticed that
SPI_scroll_cursor_move(someportal, FETCH_BACKWARD, 1);
sets S
In the absence of further feedback from 'yall (and in the presence of
some positive results from internal QA), I'm adding the posted patch
as-is to the 2008-11 CommitFest queue. That said, any such additional
feedback would be gratefully appreciated.
--
Sent via pgsql-hackers mailing list (pg
* Greg Stark <[EMAIL PROTECTED]> [081024 10:48]:
> I thought about how to support both and ran into probblems that would
> make the resulting solutions quite complex.
>
> In the libaio view of the world you initiate io and either get a
> callback or call another syscall to test if it's complet
Also keep in mind that solaris is open source these days. If someone
wants it they could always go ahead and add the feature ...
greg
On 24 Oct 2008, at 03:18 PM, Bruce Momjian <[EMAIL PROTECTED]> wrote:
Jonah H. Harris wrote:
On Fri, Oct 24, 2008 at 7:59 AM, Hannu Krosing
<[EMAIL PROTECTE
I thought about how to support both and ran into probblems that would
make the resulting solutions quite complex.
In the libaio view of the world you initiate io and either get a
callback or call another syscall to test if it's complete. Either
approach has problems for postgres. If the pro
Stefan Kaltenbrunner wrote:
there will be planned maintenance today for tribble.postgresql.org
starting 15:30 CEST today (24.10.2008) affecting the following services:
cvs.postgresql.org
wwwmaster.postgresql.org
www.pgadmin.org
doxygen.postgresql.org
wiki.postgresql.org
tribble had some unexpe
Jonah H. Harris wrote:
> On Fri, Oct 24, 2008 at 7:59 AM, Hannu Krosing <[EMAIL PROTECTED]> wrote:
> > On Fri, 2008-10-24 at 00:52 -0400, Jonah H. Harris wrote:
> >> While we could build an
> >> abstract prefetch interface and simply use fadvise for it now (rather
> >> than OS-specific code), I don
On Fri, Oct 24, 2008 at 7:59 AM, Hannu Krosing <[EMAIL PROTECTED]> wrote:
> On Fri, 2008-10-24 at 00:52 -0400, Jonah H. Harris wrote:
>> While we could build an
>> abstract prefetch interface and simply use fadvise for it now (rather
>> than OS-specific code), I don't see an easy win in any case.
>
there will be planned maintenance today for tribble.postgresql.org
starting 15:30 CEST today (24.10.2008) affecting the following services:
cvs.postgresql.org
wwwmaster.postgresql.org
www.pgadmin.org
doxygen.postgresql.org
wiki.postgresql.org
tribble had some unexpected downtimes lately so I'm
Hi All,
I would like to ask a help to Postgres-R... because have tried to use it with
any version from CVS and normal Postgres source code but could not do patch it.
What kind of form or method must be used to patch that it can work correctly?
Thanks.
Imre
On Fri, 2008-10-24 at 00:52 -0400, Jonah H. Harris wrote:
> While we could build an
> abstract prefetch interface and simply use fadvise for it now (rather
> than OS-specific code), I don't see an easy win in any case.
When building an abstract interface, always use at least two
implementations (I
KaiGai Kohei wrote:
> Simon Riggs wrote:
>> On Tue, 2008-10-21 at 18:48 +0900, KaiGai Kohei wrote:
>>
>>> I started to rework the SE-PostgreSQL documentation to catch up
>>> the latest implementation, because the existing PDF documents are
>>> a bit legacy to be updated.
>>> In addition, I moved th
Kris Jurka napsal(a):
The problem with trying to deprecate it is that the vast majority of the
backend is still using the old interfaces, so people looking for
inspiration for their external modules will likely end up using the old
interface. Like Alvaro I started this conversion a while ag
23 matches
Mail list logo
