RH7.3 is a supported distribution for at least 6 months. Any plans to add
Postgres 7.3.3 RPMs for RH7.3?
Thanks
__
Do you Yahoo!?
Yahoo! Calendar - Free online calendar with sync to Outlook(TM).
http://calendar.yahoo.com
---(end of broa
On Wed, May 28, 2003 at 11:56:07PM +0200, Peter Eisentraut wrote:
> There is a standard interface (SUSv2) for detecting the character set
> based on the locale settings. I suggest we use this (if available) in
> applications like psql and pg_dump by default unless it is overridden by
> the usual m
On Wednesday, May 28, 2003, at 07:56 PM, Tom Lane wrote:
44 0013 0002 0005 3137303632
D mesg len 2col col1 len5 oid 17602 len col2 here?
Looks fine to me. -1 length means a NULL.
Duh. I had a test for -1, but I was reading the length as an unsigned
integer. I'd have to wa
I was asked a question about Red Hat's involvement in the PGDG RPM's by
e-mail. Since at least one person was interested, I thought I would post to
the list to satisfy everyone's curiosity. At the end of this e-mail is a
Grand Unified Changelog for the RPMset. It is massive.
Back in the summ
"Yurgis Baykshtis" <[EMAIL PROTECTED]> writes:
> The problem happens only when running this query from the plpgsql
> function... So it must be a bug specific to plpgsql parser.
It's actually plpgsql trying to be helpful and detect errors.
99% of the time I think this behavior would be considered
John DeSoi <[EMAIL PROTECTED]> writes:
> I'm working on a new client with the 3.0 protocol. I'm having a problem
> with the data DataRow message from this select:
> select oid, datconfig from pg_database
> There seems to be a problem with text[] type for datconfig. The hex
> dump (from tcpflow)
Peter Eisentraut <[EMAIL PROTECTED]> writes:
> There is a standard interface (SUSv2) for detecting the character set
> based on the locale settings.
Hmm. How trustworthy is that really?
If it works, great, but I wonder if we wouldn't be chasing a
will-o-the=wisp. My impression is that LC_xxx se
I strongly object this idea. We already have had enough trouble with
initdb because of its locale awareness (I still think we should turn
on the --no-locale switch by default).
--
Tatsuo Ishii
> It is a common problem that a server uses a nontrivial character set
> encoding (e.g., Unicode) but use
It is a common problem that a server uses a nontrivial character set
encoding (e.g., Unicode) but users forget to set an appropriate
client-side encoding. Then they get bogus displays for non-ASCII
characters because their client isn't actually prepared for Unicode.
There is a standard interface
I'm working on a new client with the 3.0 protocol. I'm having a problem
with the data DataRow message from this select:
select oid, datconfig from pg_database
There seems to be a problem with text[] type for datconfig. The hex
dump (from tcpflow) for 1 data row message is:
44 0013 0002 00
The problem happens only when running this query from the plpgsql
function... So it must be a bug specific to plpgsql parser.
-Original Message-
From: Yurgis Baykshtis
Sent: Wednesday, May 28, 2003 1:07 PM
To: [EMAIL PROTECTED]
Subject: Mismatched parentheses when creating a rule with mu
Srikanth M wrote:
Hi!
I am interested in adding DATA-CUBE operator(Related to Data
Warehousing) to postgresql. I just want to know wheather it is already
added to postgres or not. please reply to this mail if you have already
worked or still working on it.
Bye
Srikanth
PostgreSQL 7.3.2.
The parser does not seem to like semicolon between action queries:
(Mismatched parentheses)
So, it makes impossible to create a rule with more than one action
query.
Or am I missing something?
CREATE RULE my_insert_rule AS ON INSERT
TO my_view
DO INSTEAD
(
INSERT IN
"Christopher Kings-Lynne" <[EMAIL PROTECTED]> writes:
> I actually like the NEXT VALUE FOR a lot more. The reason is that the
> Oracle syntax is very much an 'object.property' lookup, which we do nowhere
> else in PostgreSQL.
I beg to differ. We have supported table.function since day one ---
it
"Christopher Kings-Lynne" <[EMAIL PROTECTED]> writes:
>> There's been some past speculation about putting in a function call
>> nesting depth limit, but I haven't been able to think of any reasonable
>> way to estimate a safe limit.
> GUC variable? Hmm...but that would mean that a normal user cou
Is it possible to get the transaction ID of the transaction a trigger
fired on from plpgsql?
I see in postgresql/contrib/dbmirror/pending.c a C based stored procedure
that is accessing this information. I can't find anything in the online
docs for accessing the xid from plpgsql.
Brian Knox
[EMAI
Hi!
I am interested in adding DATA-CUBE operator(Related to Data
Warehousing) to postgresql. I just want to know wheather it is already
added to postgres or not. please reply to this mail if you have already
worked or still working on it.
Bye
Srikanth
---(end o
On Thursday 13 February 2003 22:24, Joe Conway wrote:
> Peter Eisentraut wrote:
> > Joe Conway writes:
> >>So I wrote a quick hack to load and initialize the library on postmaster
> >>startup.
> >
> > On glibc systems you can probably do this using the environment variable
> > LD_PRELOAD. I guess
On Wed, May 28, 2003 at 12:59:56PM +0200, Sailesh Krishnamurthy wrote:
> elog(NOTICE should send NOTICE messages to the psql client (I think !)
> while elog(LOG while only send it to the logfile you might have
> specified while starting the postmaster
Whether a given elog level is sent to the po
On Wed, May 28, 2003 at 09:04:18AM -0400, Michael Brusser wrote:
> > Well, first thing I'd ask is whether the other installation is using
> > the same locale settings.
> Oh, yes, I am very sure of that.
Note that while the machine reports the C locale, pg_controldata
actually said the database was
20 matches
Mail list logo