I've been looking into the code of psql to fix a problem with charsets and
noticed that psql changes the strings it gets back from functions like
PQfname() and PQgetvalue().
I can't find in the docs anything that says that it is okay to alter the
returned string. It works since it's allocated and
Hi,
I would like to know if in the Windows installer
version, you still plan to use cygwin to setup
PostgreSQL ?
If no, how do you setup files and parameters ?
Moreover, What are the traps to pay attention when we
install PostgreSQL on Windows ?
tia,
X04001
__
D
Patch applied. Thanks.
---
Darko Prenosil wrote:
> I have noticed that after "/etc/init.d/postgresql restart", postmaster is no
> longer writes to "serverlog". (RedHat 9).
> Here is fixed "restart" section.
>
> res
sorry for delay ... installing opensp right now ...
On Sun, 1 Jun 2003, Peter Eisentraut wrote:
> Tom Lane writes:
>
> > (the documentation build at developer.postgresql.org doesn't seem to
> > have updated since before the server move :-()
>
> The program called "onsgmls" (or maybe "nsgmls") i
On Wed, Jun 11, 2003 at 07:35:20PM -0400, Doug McNaught wrote:
> Bruce Momjian <[EMAIL PROTECTED]> writes:
>
> > Is there no sysctl way to disable such kills?
>
> The -ac kernel patches from Alan Cox have a sysctl to control memory
> overcommit--you can set it to track memory usage and fail alloc
Bruce Momjian <[EMAIL PROTECTED]> writes:
> Tom Lane wrote:
> > AFAIK the only good way around this problem is to use another OS with a
> > more rational design for handling low-memory situations. No other Unix
> > does anything remotely as brain-dead as what Linux does. Or bug your
> > favorite
On Wed, 2003-06-11 at 08:03, Bruno Wolff III wrote:
> On Tue, Jun 10, 2003 at 22:34:04 -0700,
> "P.M" <[EMAIL PROTECTED]> wrote:
> >
> > I was thinking that PostgreSQL could help me to reduce
> > the cost of a such software. But i would like to know
> > what is the status of the PostGreSQL versi
Tom Lane wrote:
> =?ISO-8859-1?Q?Hans-J=FCrgen_Sch=F6nig?= <[EMAIL PROTECTED]> writes:
> > I have two explanations for the following behaviour:
> > a. a bug
> > b. not enough shared memory
>
> > WARNING: Message from PostgreSQL backend:
> > The Postmaster has informed me that some other backe
=?ISO-8859-1?Q?Hans-J=FCrgen_Sch=F6nig?= <[EMAIL PROTECTED]> writes:
> I have two explanations for the following behaviour:
> a. a bug
> b. not enough shared memory
> WARNING: Message from PostgreSQL backend:
> The Postmaster has informed me that some other backend
> died abnormally a
> >Yes, a combination of the two would probably be better. You would need
> >to be careful about function call names for FKeys, there are a fair
> >number of them. Checking for 3 triggers with the function name starting
> >with RI_FKey* would probably be better.
>
> Will the tgisconstraint flag
Thanks. Fixed.
---
Tom Lane wrote:
> Bruce Momjian <[EMAIL PROTECTED]> writes:
> > Patch applied. You patch indicated _int.c should be removed from CVS,
> > so I have done so.
>
> This patch causes contrib/intarray to fai
"Jim C. Nasby" <[EMAIL PROTECTED]> writes:
> Is it really necessary to block reads on a table that is affected by
> adding a foreign key constraint?
It's trickier than you seem to think. The command is adding an index,
which at some point is going to affect plans for SELECTs on the table.
It migh
Tom Lane wrote:
Peter Eisentraut <[EMAIL PROTECTED]> writes:
... Therefore I ask whether everyone agrees
that groups and roles are basically equivalent concepts (and perhaps that
we might in the future strive to make groups more compatible with the
roles as defined in the SQL standard). Or does a
Bruce Momjian <[EMAIL PROTECTED]> writes:
> Patch applied. You patch indicated _int.c should be removed from CVS,
> so I have done so.
This patch causes contrib/intarray to fail to build.
$ make
sed 's,MODULE_PATHNAME,$libdir/_int,g' _int.sql.in >_int.sql
make: *** No rule to make target `_int_b
I don't think that this has been up for discussion yet but I think it
would be good concept/feature that someone might want to take up or
shoot down. However some may have already. I am not sure where it falls
PGAdmin, psql, optimizer, gborg... all.
Recommended Feature: Index Tuning Wizard
Des
Hi folks,
We recently built a dual K8D-based Opteron box running Linux in 64-bit
mode (Debian 'testing' distribution with newly compiled binutils, gcc,
and various support libraries for amd64 architecture).
The Postgres 7.3.3 "port" was simply a matter of setting the appropriate
flags to take of
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Monday 02 June 2003 10:19, Tom Lane wrote:
> * Better FunctionCall API?
>
> nah, just deprecate in favor of invoking the function via
> PQexecParams().
>
I'll admit -- the current state of PQfn is practically unuseable. However, the
id
>On Thursday 29 May 2003 17:41, Sander Steffann wrote:
>> Someone else has already built RPMs for RH73 and Lamar has already
uploaded
>> them to ftp.postgresql.org. I just completed the RH62 packages. Lamar
will
>> put them on the FTP server, but until then they can be picked up from
>> http://www
Bruce Momjian wrote:
We already pre-allocate all shared memory and resources on postmaster
start.
I guess we allocate memory when a backend starts, don't we?
Or do we allocate when the instance starts?
I have two explanations for the following behaviour:
a. a bug
b. not enough shared memory
WARN
Patch applied. You patch indicated _int.c should be removed from CVS,
so I have done so.
---
Teodor Sigaev wrote:
> Patch for contrib/intarray and contrib/ltree modules.
>
> Download from:
> http://www.sai.msu.su/~megera/
Is it really necessary to block reads on a table that is affected by
adding a foreign key constraint? I can see why you wouldn't want UPDATES
or INSERTS on the child table or DELETEs on the parent, but select
should be fine on both tables, no?
--
Jim C. Nasby (aka Decibel!)[EMA
Rod Taylor <[EMAIL PROTECTED]> wrote:
>> Unfortunately, having all my users run contrib/adddepend isn't an
>> option for me. However, that script does contain a good deal of
>> information that I may be able to use for detecting old-style foreign
>> key constraints in my own code.
>
>I assume you
>> We've discussed a couple of times allowing the parser to "interrogate"
>> the function at parse time to let it determine what the runtime tupdesc
>> will be, but I haven't been able to come up with a good way to do that.
This seems fairly unworkable to me, as in interesting cases the parser
c
You could actually get the tupdesc from the caller if you wanted. See,
for example crosstab_hash() in contrib/tablefunc:
/* check to see if caller supports us returning a tuplestore */
if (!rsinfo || !(rsinfo->allowedModes & SFRM_Materialize))
elog(ERROR, "crosstab: materialize mode requ
We already pre-allocate all shared memory and resources on postmaster
start.
---
Hans-Jürgen Schönig wrote:
> There is a problem which occurs from time to time and which is a bit
> nasty in business environments.
> When the
Teodor Sigaev wrote:
it's a great pity :(.
But in function I already make TupleDesc:
tupdesc = CreateTemplateTupleDesc(attnum, false);
for (i = 0; i < attnum; i++) {
sprintf(attname, "z%d", i+1);
TupleDescInitEntry(tupdesc, i+1, attname, INT4OID, -1
There is a problem which occurs from time to time and which is a bit
nasty in business environments.
When the shared memory is eaten up by some application such as Apache
PostgreSQL will refuse to do what it should do because there is no
memory around. To many people this looks like a problem re
> Hi,
> could somebody explain me please why following select
> SELECT docid FROM prod.guids
> GROUP BY docid HAVING( COUNT(docid) > 1 )
>
> taking 15 min on 2 Proc Box on 1M rows, where number of duplicates
> around 300K,
> and docid indexed and not null and char(16).
>
> May be I am doin
BTW, in case anyone else besides me wasn't up to speed, the
anonymous-CVS mirror is functioning again. It is at the same
place as before:
:pserver:[EMAIL PROTECTED]:/projects/cvsroot
The only change from previously published instructions is that you have
to give some nonempty password (doesn't m
> Hi,
>
> I'm new in this mailing list and in the world of
> PostGreSQL.
>
> I need to create a C++ application under Windows which
> will use a very huge database...
>
> I was thinking that PostgreSQL could help me to reduce
> the cost of a such software. But i would like to know
> what is the
shoujld be fixed now
On Wed, 11 Jun 2003, Tom Lane wrote:
> ... pgsql-committers is not propagating. Bruce evidently applied
> a ton of patches last night, and I see no committers messages for
> any of 'em.
>
> regards, tom lane
>
> ---(end of broad
Manfred Koizar <[EMAIL PROTECTED]> writes:
> If a transaction marks a tuple for update and later commits without
> actually having updated the tuple, do we still need the information
> that the tuple has once been reserved for an update or can we simply
> set the HEAP_XMAX_INVALID hint bit of the t
... pgsql-committers is not propagating. Bruce evidently applied
a ton of patches last night, and I see no committers messages for
any of 'em.
regards, tom lane
---(end of broadcast)---
TIP 4: Don't 'kill -9' the postmaster
On Tue, Jun 10, 2003 at 22:34:04 -0700,
"P.M" <[EMAIL PROTECTED]> wrote:
>
> I was thinking that PostgreSQL could help me to reduce
> the cost of a such software. But i would like to know
> what is the status of the PostGreSQL version under
> Windows ?
> I mean, i know that some of you are tryin
It works fine. But is there way not to point 'as c(qq int4, qq1 int4)'?
If you mean, is there a way to leave out the 'as c(qq int4, qq1 int4)',
the answer is no. You need to either declare the function to return a
determinate data type, or you have to specify the data type at runtime
in the
If a transaction marks a tuple for update and later commits without
actually having updated the tuple, do we still need the information
that the tuple has once been reserved for an update or can we simply
set the HEAP_XMAX_INVALID hint bit of the tuple?
In other words, is this snippet from a patch
36 matches
Mail list logo
