Re: [GENERAL] error messages
On Oct 5, 4:19 am, amikl...@freemail.hu (Miklosi Attila) wrote: > Dear Postgres! > > We have just moved our database to a more powerful pc and since then we > keep getting this strange error message below: > "PGRES_FATAL_ERROR FATAL: invalid frontend message type 87" > > What does this message mean? What could cause this error? Are you using the correct version of your psql command-line tool? This error seems familiar from back when I tried to do this once. -- The Lumber Cartel, local 42 (Canadian branch) Beautiful British Columbia, Canada http://www.lumbercartel.ca/ -- Sent via pgsql-general mailing list (pgsql-general@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-general
Re: [GENERAL] PG website testing
On Oct 4, 11:40 am, t...@linux.com (Thom Brown) wrote: > Hi all, > > We're currently testing a new javascript change on the PostgreSQL > docs. This is to make sure monospaced fonts still appear at a > reasonable size between browsers. I'd appreciate it if some of you > could do some browser testing. http://magnus.webdev.postgresql.org/ > Only docs for 8.3 and below are available. Please also check the main > site for font issues, and post any issues you find here. > > Thanks :) I'm using Opera 10 on Windows 7 (64-bit), and the fonts look good (professional, as usual), and also appear to have the correct proportions when I use Opera's built-in zoom feature to shrink or enlarge the page view. I also really like the rounded corners for the slightly darker (just the right amount in my opinion) boxes around the fixed-width fonts, such as can be seen on this page: http://magnus.webdev.postgresql.org/docs/8.3/interactive/sql-listen.html One suggestion (low priority, but would be nice to have), just in case you're interested: Make the keywords link to their respective pages from this page: http://magnus.webdev.postgresql.org/docs/8.3/interactive/sql-keywords-appendix.html -- The Lumber Cartel, local 42 (Canadian branch) Beautiful British Columbia, Canada http://www.lumbercartel.ca/ -- Sent via pgsql-general mailing list (pgsql-general@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-general
Re: [GENERAL] How to data dump a table content to a CSV or XML format?
On Oct 4, 4:35 pm, li...@remoteinformation.com.au (Ben Madin) wrote:
> Or in psql you can look at the help (\?) and set the output format to
> unaligned, comma separated, and output the table to disk :
[sNip]
> > I'd like to do a data dump of a table to a CSV or XML file.
> > How would I do that?
[sNip]
> database=> \pset fieldsep ,
> Field separator is ",".
> database=> \a
> Output format is unaligned.
> database=> \o table.csv
> database=> SELECT * FROM table;
> database=> \o
[sNip]
This is a good solution as long as none of the column data includes
comma characters.
Since commas are more likely to occur in CHAR/VARCHAR/TEXT/etc.
columns than tabs, I suggest using something like this instead
(assuming none of your columns contain tab {ASCII 9} characters):
database=> \pset fieldsep '\t'
Field separator is "".
database=> \a
Output format is unaligned
database=> \o table.tab
database=> TABLE table;
database=> \o
--
The Lumber Cartel, local 42 (Canadian branch)
Beautiful British Columbia, Canada
http://www.lumbercartel.ca/
--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-general
Re: [GENERAL] Win2k? Really?
On Oct 3, 10:58 pm, cr...@postnewspapers.com.au (Craig Ringer) wrote: [sNip] > Should win2k be declared dead and dropped from the supported platform > list? It's over 10 years old, after all, and there's no evidence it's > tested anymore. [sNip] I have one client who still uses Windows 2000, but it's not because of budgetary or technical issues, rather it's a matter of personal preference for the developer -- we're slowly getting him over to Windows XP (this project to move to XP has been going on for many years). For all my other clients who used Windows 2000 at some point, many of them have long ago upgraded to XP or 2003 or Vista, and today most are on NetBSD Unix (after the disaster that was Vista, it was dead-easy to convince people to switch to Unix for their database server needs). I'm not concerned about Windows 2000 support at all. What I do like is that PostgreSQL 9 supports 64-bit Windows natively because all the Windows 7 installations I've been involved in are 64-bit (the only reason I would approve 32-bit is when there is a specific hardware limitation, but that's usually cured quite easily with more money). -- The Lumber Cartel, local 42 (Canadian branch) Beautiful British Columbia, Canada http://www.lumbercartel.ca/ -- Sent via pgsql-general mailing list (pgsql-general@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-general
