I just committed the attached small fix to CVS HEAD and the 8.3 branch.
This should fix your problem.
Michael
--
Michael Meskes
Email: Michael at Fam-Meskes dot De, Michael at Meskes dot (De|Com|Net|Org)
ICQ: 179140304, AIM/Yahoo: michaelmeskes, Jabber: [EMAIL PROTECTED]
Go VfL Borussia! Go SF
Andrej Ricnik-Bay wrote:
On 23/02/2008, David Jaquay [EMAIL PROTECTED] wrote:
When I do a ps -ef, in the command column, I see:
postgres: postgres dbname 10.170.1.60(57413) idle
This doesn't resemble any ps -ef output I've ever seen.
What OS is this on, what's the version of ps?
I had
I am building a web app with Postgres, that also uses Drupal with Postgres.
I am new to all these frameworks.
There is some data that I'll need to cross-reference between the two
databases.
Can I do a cross-schema/catalog join? Or is a cross-database join better?
Are there any gotchas for the
Ugh.
I am attempting to move from 8.2.6 to 8.3, and have run into a major
problem.
The build goes fine, the install goes fine, the pg_dumpall goes fine.
However, the reload does not. I do the initdb and then during the
reload I get thousands of errors, apparently from table data which is
On Sun, Mar 2, 2008 at 1:54 PM, Swaminathan Saikumar [EMAIL PROTECTED] wrote:
I am building a web app with Postgres, that also uses Drupal with Postgres.
I am new to all these frameworks.
There is some data that I'll need to cross-reference between the two
databases.
Can I do a
On Sun, Mar 2, 2008 at 1:41 PM, Karl Denninger [EMAIL PROTECTED] wrote:
Ugh.
I am attempting to move from 8.2.6 to 8.3, and have run into a major
problem.
The build goes fine, the install goes fine, the pg_dumpall goes fine.
However, the reload does not. I do the initdb and then
I am familiar with MS Sql Server just started using Postgres.
For storing Unicode, Sql Server uses nvarchar/char for unicode, and uses
char/varchar for ASCII.
Postgres has this encoding setting at the database level.
I am using UTF8 Unicode for most of my data, but there is some data that I
know
On Sun, Mar 02, 2008 at 11:50:01AM -0800,
Swaminathan Saikumar [EMAIL PROTECTED] wrote
a message of 30 lines which said:
Postgres has this encoding setting at the database level.
Which is simpler, IMHO. One encoding to rule them all
I am using UTF8 Unicode for most of my data, but there is
A whole host of them, mostly about bad data formats in some of the table
data. I suspect the underlying problem is that something got mangled in
the table creates.
I'm setting up on a different box as my attempt to create a second
instance failed horribly - compiling with a different prefix
Swaminathan Saikumar wrote:
I didn't have proper knowledge about the UTF8 format, thanks.
I originally meant nvarchar nchar, which is basically varchar char
that supports Unicode regardless of the database encoding.
Well, we don't need that when we have UTF8. There could be edge cases
speed
Swaminathan Saikumar wrote:
I am familiar with MS Sql Server just started using Postgres.
For storing Unicode, Sql Server uses nvarchar/char for unicode, and uses
char/varchar for ASCII.
Postgres has this encoding setting at the database level.
I am using UTF8 Unicode for most of my data,
I didn't have proper knowledge about the UTF8 format, thanks.
I originally meant nvarchar nchar, which is basically varchar char that
supports Unicode regardless of the database encoding.
On 3/2/08, Tino Wildenhain [EMAIL PROTECTED] wrote:
Swaminathan Saikumar wrote:
I am familiar with MS
Scott Marlowe wrote:
On Sun, Mar 2, 2008 at 1:41 PM, Karl Denninger [EMAIL PROTECTED] wrote:
Ugh.
I am attempting to move from 8.2.6 to 8.3, and have run into a major
problem.
The build goes fine, the install goes fine, the pg_dumpall goes fine.
However, the reload does not. I do the
On Sunday 2. March 2008, Swaminathan Saikumar wrote:
I am using UTF8 Unicode for most of my data, but there is some data
that I know for sure will be ASCII. However, this is also stored as
UTF8, using up more space.
ASCII stored as UTF8 doesn't take up more space than plain ASCII, it's
exactly
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Sun, 02 Mar 2008 15:46:25 -0600
Karl Denninger [EMAIL PROTECTED] wrote:
I'm not quite clear what I have to do in terms of if/when I can drop
the old tsearch config stuff and for obvious reasons (like not
running into this in the future) I'd
Karl Denninger [EMAIL PROTECTED] writes:
It looks like the problem had to do with the tsearch2 module that I have
in use in a number of my databases, and which had propagated into
template1, which meant that new creates had it in there.
The old tsearch2 module isn't at all compatible with
Tom Lane wrote:
Karl Denninger [EMAIL PROTECTED] writes:
It looks like the problem had to do with the tsearch2 module that I have
in use in a number of my databases, and which had propagated into
template1, which meant that new creates had it in there.
The old tsearch2 module isn't
Joshua D. Drake wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Sun, 02 Mar 2008 15:46:25 -0600
Karl Denninger [EMAIL PROTECTED] wrote:
I'm not quite clear what I have to do in terms of if/when I can drop
the old tsearch config stuff and for obvious reasons (like not
running into
Last month there was a discussion about how it would be nice to have a
place people would write user-oriented documentation at with more
flexibility than the current Techdocs site offers. I ran with that idea
and there is now such a site available at http://www.postgresqldocs.org
You will
Greg Smith wrote:
Thanks to Joshua Drake and Command Prompt for providing hosting space
and even having an appropriate domain. To cut off one question I expect
to pop up, yes it would be nice to have this integrated with the main
postgresql.org site and its existing account structure. But
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Mon, 03 Mar 2008 00:47:09 -0500
Guy Rouillier [EMAIL PROTECTED] wrote:
Greg et al, thanks very much for taking this idea and making it a
reality. Since I was one of the ones who requested it, I'll sign up
for an account right away (done).
21 matches
Mail list logo
