Bruce Momjian [EMAIL PROTECTED] writes:
Are you 64-bit s390?
The patch is for GNU/Linux on S/390 hardware. This platform is sane
and it uses ASCII.
Only the traditional UNIX subsystem for OS/390 uses EBCDIC.
--
Florian Weimer[EMAIL PROTECTED]
University of Stuttgart
What do the columns conforencoding and contoencoding refer to in
pg_conversion?
How would I convert those numbers to a string encoding name, just using SQL?
Chris
Use pg_encoding_to_char().
--
Tatsuo Ishii
---(end of broadcast)---
TIP 2:
On December 6, 2002 02:10 pm, Bruce Momjian wrote:
It should lock only the rows you retrieved, but I have no idea how FOR
UPDATE and INTO TEMP behave. My guess is that it should work fine, but
I have never seen those two used together before.
Turns out that it wasn't the SELECT ... FOR UPDATE
Bruce Momjian [EMAIL PROTECTED] writes:
I am pretty sure it is going to fail if your machine isn't INET6 aware,
which may be many.
That's definitely not gonna do :-(
regards, tom lane
---(end of broadcast)---
TIP 1:
Bruce Momjian [EMAIL PROTECTED] writes:
You would think that would catch it. My problem is that I am compiling
with -O0, because I compile all day and I don't care about optimization.
You should reconsider that. At -O0 gcc doesn't do any flow analysis,
and thus you lose many important
On Wed, 4 Dec 2002, Bruce Momjian wrote:
Peter Eisentraut wrote:
Marc G. Fournier writes:
It isn't, but those working on -advocacy were asked to help come up with a
stronger release *announcement* then we've had in the past ...
Consider that a failed experiment. PostgreSQL is
Vince Vielhaber wrote:
On Thu, 5 Dec 2002, Robert Treat wrote:
Well, my previous employer uses postgresql, but they were under constant
assault from their clients to use oracle or db2. Technically there was no
reason to switch, but if your choice is switch databases or go out of
business,
On Thu, 5 Dec 2002, Brian Knox wrote:
Speaking from the perspective of a long time postgresql user, who
currently has several very mission critical applications using postgresql
on the back end, at a very large company...
I can say the one consequence of the problem that I have run into
All,
I've simplified the Darwin/Mac OS X startup script I submitted earlier
in the year. This version has only the two files required by the Darwin
startup bundle design. Plus the sh script now uses Darwin-standard
functions to start up PostgreSQL, and it checks for the presence of a
variable
Hi folks,
Let's create a release team. This strategy is one well established
in other projects and in industry. For lack of a better starting
reference, let me suggest http://www.freebsd.org/releng/charter.html
as a starting point for consideration. See also
What too many people fail to realize is that in a commercial environment
many companies want another company to point the finger at in case of
disaster. Sybase failed, or HP failed, or IBM failed, or Microsoft
failed. They feel they can do something about that. If they lose a
few million
On 5 Dec 2002, Robert Treat wrote:
On Thu, 2002-12-05 at 03:28, Dave Page wrote:
www is a closed group consisting of a few of us who actually do the work
on the sites.
This is one of the primary reasons the sites are so fractured. We have 4
different mailing lists for website development
On Fri, 6 Dec 2002, Josh Berkus wrote:
Dave,
BTW, we do coordinate with the Website development group
When did that happen then? I think I must have blinked :-)
Marc and Justin are periodically keeping the Advocacy group informed
of progress on wwwdevel, and we were asked to test
13 matches
Mail list logo
