Simon Riggs <[EMAIL PROTECTED]> wrote:
> > Furthermore, this patch detaches empty fsmpages then.
> Does that do anything useful though?
> I thought we don't reallocate until VACUUM time, whereupon we identify
> any empty slots and reuse them. Who cares whether we deallocate earlier?
Yes, we canno
On Tue, 24 May 2005 01:26 am, --= Tono =-- wrote:
> I have tried using INSTEAD rules but there are some
> conditional logic that needs to happen inside the rule
> (performing counts, getting and storing the primary
> key of the master record etc.). AFAIK, rules only
> allows conditional logic to b
I tried using SELECTs inside of RULEs, but as I already explained in
this mail thread, the problem is, that a SELECT creates a result set,
which can not be discarded in SQL. This makes trouble when using
asynchronous command processing.
I have tried to modify my application in order to get a w
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi all,
I'm trying to install 8.0.3 on a RH9.0.
I do have few problems:
1) They do not exist for 9.0
2) Using the 8.0.2 rpm I get:
# rpm -Uvh --test *.rpm
warning: postgresql-8.0.2-1PGDG.i686.rpm: V3 DSA signature: NOKEY, key ID
748f7d0e
error: Fail
Check the archives, this has already been discussed.
Devrim is posting a compat rpm shortly.
Dave
Gaetano Mendola wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi all,
I'm trying to install 8.0.3 on a RH9.0.
I do have few problems:
1) They do not exist for 9.0
2) Using the 8.0.2 rpm I
Simon Riggs <[EMAIL PROTECTED]> writes:
> Would we use the -x switch if we had it?
Dunno. Depending on such a thing would require depending on a new flex
version, and seeing that the flex guys haven't put out a new release
since the badly broken 2.5.31 more than 2 years ago, I wouldn't hold
my br
""Jan B."" <[EMAIL PROTECTED]> wrote in message news:[EMAIL PROTECTED]
>I tried using SELECTs inside of RULEs, but as I already explained in this
>mail thread, the problem is, that a SELECT creates a result set, which can
>not be discarded in SQL. This makes trouble when using asynchronous comman
"Jan B." <[EMAIL PROTECTED]> writes:
> Does anyone know, if it is intended that one query can create multiple
> result tables with some of them carrying an empty string as cmdStatus?
> Perhaps this is a bug?
Yes it is, and no it isn't. Check the archives --- there was extensive
discussion of wh
Dave Cramer wrote:
> Check the archives, this has already been discussed.
> Devrim is posting a compat rpm shortly.
Thx.
Regards
Gaetano Mendola
---(end of broadcast)---
TIP 1: subscribe and unsubscribe commands go to [EMAIL PROTECTED]
You can find it here if you need it quickly
http://postgresql.gunduz.org/rpms/compat-postgresql-libs-3-1PGDG.i686.rpm
Dave
Gaetano Mendola wrote:
Dave Cramer wrote:
Check the archives, this has already been discussed.
Devrim is posting a compat rpm shortly.
Thx.
Regards
Gaetano Me
I've been working on adding the functionality into the jdbc driver and
I'm having some issues.
Currently the bind message does not know anything about directionality
of the parameter. This means that considerable gyrations need to be done
by the driver to transform
create function foo( out p
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi Gaetano,
On Tue, 24 May 2005, Dave Cramer wrote:
You can find it here if you need it quickly
http://postgresql.gunduz.org/rpms/compat-postgresql-libs-3-1PGDG.i686.rpm
Yeah, that package was tested on 5 platforms. Also Dave Cramer confirmed
t
Dave Cramer <[EMAIL PROTECTED]> writes:
> On a related note, drop function needs to support the in/out direction.
It does ... do you see a problem?
regards, tom lane
---(end of broadcast)---
TIP 2: you can get off all lists
Hi,
I was redirected to this maillist when i asked questions on irc. I
hope this is the right mailing list.
I am running postgresql 7.4.8 on solaris 10 (and I compile and
installed slony). Everytime I am trying to reload the configuration
using pg_ctl reload -D $PGDATA, it deleted the postmaster.pi
H
> It seems to me that the bind message needs to support the notion of
> direction in order for this to work cleanly.
>
> Alternatively we could punt and use SQL Server's mechanism where they
> only support IN, and INOUT, which would require all parameters to be
> sent to the procedure.
Junaili,
> I am running postgresql 7.4.8 on solaris 10 (and I compile and
> installed slony). Everytime I am trying to reload the configuration
> using pg_ctl reload -D $PGDATA, it deleted the postmaster.pid and
> didn't create a new one. So, after reload, the only way I can restart
> the server i
Dave Cramer <[EMAIL PROTECTED]> writes:
> create function foo( out p1 int, in p2 int, out p3 int)
> then a subsequent
> "{call = select foo(?,?,?)}
> This would need to be currently transformed into select foo(?), with the
> other two being discarded.
> It seems to me that the bind mess
Junaili Lie <[EMAIL PROTECTED]> writes:
> I am running postgresql 7.4.8 on solaris 10 (and I compile and
> installed slony). Everytime I am trying to reload the configuration
> using pg_ctl reload -D $PGDATA, it deleted the postmaster.pid and
> didn't create a new one.
That's very strange. The pg
Ok, then I guess the documentation needs to indicate that. Or the
version I am reading is not up to date.
Dave
Tom Lane wrote:
Dave Cramer <[EMAIL PROTECTED]> writes:
On a related note, drop function needs to support the in/out direction.
It does ... do you see a probl
At this point I'd just like the backend to ignore the OUT parameter if
it were set that way, but allow
it to be sent.
If you consider that a function could have for arguments sake 10
parameters, and they
can be ordered in any fashion; clients have to essentially parse out the
OUT parameters an
Tom,
> How would it help for BIND to incorporate direction? What would it even
> *mean* for BIND to incorporate direction --- it's a client-to-server
> message, and can hardly be expected to transmit data in the reverse
> direction.
Where directionality comes in is with OUT-only parameters. Wh
Folks,
> > > I am running postgresql 7.4.8 on solaris 10 (and I compile and
> > > installed slony). Everytime I am trying to reload the configuration
> > > using pg_ctl reload -D $PGDATA, it deleted the postmaster.pid and
> > > didn't create a new one. So, after reload, the only way I can restart
Dave Cramer <[EMAIL PROTECTED]> writes:
> At this point I'd just like the backend to ignore the OUT parameter if
> it were set that way, but allow it to be sent.
I think you're thinking at the wrong level. AIUI the issue occurs at
the Parse stage, long before any parameter value is sent (or not
Josh Berkus writes:
> Looking at his report, what's happening is that the postmaster is shutting
> down, but the other backends are not ... they're hanging around as
> zombies.
The zombies couldn't be dead backends if the postmaster has gone away:
in every Unix I know, a zombie process disappear
Dave Cramer <[EMAIL PROTECTED]> writes:
> Ok, then I guess the documentation needs to indicate that. Or the
> version I am reading is not up to date.
Oh, you're right, I overlooked adding that to the documentation of
the other statement types that work with function names.
Come to think of it, t
Tom,
> The zombies couldn't be dead backends if the postmaster has gone away:
> in every Unix I know, a zombie process disappears instantly if its
> parent dies (since the only reason for a zombie in the first place
> is to hold the process' exit status until the parent reads it with
> wait()).
y
Hi,
Thank you all for the respond.
I should probably mentioned that postgres is maintained by smf, which
is a service management tool in solaris 10.
I asked our sys admin to remove postgres from being managed by smf.
he did that. But right now he is having problem because the system
could not start
Hey everyone,
I've been working with a couple people who didn't know that soundex and
metaphone were included in the distribution as contrib modules. While
it's their fault that they didn't check contrib, soundex is pretty
common among database systems and I was wondering if there was a reaso
Tom,
I am not too sure how to determine the unlink call.
Can you provide more information/instructions?
In my case the pg_ctl reload -D /usr/local/pgsql deleted the
postmaster.pid without creating a new one. I am not too sure if this
is normal.
J
On 5/24/05, Tom Lane <[EMAIL PROTECTED]> wrote:
People:
OK, found it in SQL99:
::=
[ ] [ ] [ RESULT ]
::=
IN
| OUT
| INOUT
... so this is something we need to support, apparently both for Functions and
Procedures (when we get the latter), in the backend, not just JDBC. As you
can imagine, though, SQL03 does nothing to clarify ca
Tom Lane wrote:
Dunno. Depending on such a thing would require depending on a new flex
version, and seeing that the flex guys haven't put out a new release
since the badly broken 2.5.31 more than 2 years ago, I wouldn't hold
my breath waiting for one we can use.
It should be easy enough to che
Zeljko Vrba <[EMAIL PROTECTED]> writes:
> Is there yet another way of making WHERE field = ANY (subselect
> returning an array) work? Or make postgres to use index?
You could use the int_array_enum() function from the contrib/int_agg module.
> Also, what is the limit on the number of elements i
Tom Lane <[EMAIL PROTECTED]> writes:
> The EXPLAIN ANALYZE overhead for the Append is still pretty heavy,
> but when comparing actual runtimes for the two queries, they are
> now very nearly the same.
How hard would it be to have Postgres actually remove the gettimeofday
overhead from the EXPLAI
33 matches
Mail list logo
