to use MySQL are scurvy dogs.
I fear you've jumped the gun, sir - Talk Like A Pirate Day isn't until
tomorrow :-).
Ron Johnson, Jr.
Tim
--
---
Tim Allen [EMAIL PROTECTED]
Proximity Pty Ltd http://www.proximity.com.au
his opinion rather than
tell him it's not his business.
Tim
--
---
Tim Allen [EMAIL PROTECTED]
Proximity Pty Ltd http://www.proximity.com.au/
---(end of broadcast)---
TIP 1: if posting/reading
Q3C module for POstgreSQL (q3c.sf.net). We use it for providing access
to very big astronomical catalogs.
Oleg
Tim
--
---
Tim Allen [EMAIL PROTECTED]
Proximity Pty Ltd http://www.proximity.com.au/
---(end
_delighted_ that the core postgres developers
spend their time improving postgres, rather than spending their time on
random beauty contests.
Tim
--
---
Tim Allen [EMAIL PROTECTED]
Proximity Pty Ltd http://www.proximity.com.au
cannot see how at the
moment...
I can't see it either :). Decide what you want to do first, _then_ work
out how to implement it.
Tim
--
---
Tim Allen [EMAIL PROTECTED]
Proximity Pty Ltd http://www.proximity.com.au
experience,
so I could be wrong.
Tim
--
---
Tim Allen [EMAIL PROTECTED]
Proximity Pty Ltd http://www.proximity.com.au/
---(end of broadcast)---
TIP 3: Have you checked our extensive FAQ
it happen (no
telling how long that will be), or helping to make it happen (for which
we would all thank you :-) ). In the meantime you'll have to work around
it, as you suggested.
Tim
--
---
Tim Allen [EMAIL PROTECTED]
Proximity Pty Ltd http
--
---
Tim Allen [EMAIL PROTECTED]
Proximity Pty Ltd http://www.proximity.com.au/
---(end of broadcast)---
TIP 3: Have you checked our extensive FAQ?
http://www.postgresql.org/docs/faq
Tino Wildenhain wrote:
Tim Allen schrieb:
[snip]
The way to tell PostgreSQL what encoding you want to use is by use of
the client_encoding GUC variable, eg
set client_encoding to 'LATIN1';
If you cant educate your client application to set this option on connect,
you can set this per
--
---
Tim Allen [EMAIL PROTECTED]
Proximity Pty Ltd http://www.proximity.com.au/
---(end of broadcast)---
TIP 6: explain analyze is your friend
is considered to be acceptable, if not good, practice on
all other platforms and distributions too. If a particular build would be
totally broken/untested/known to eat your soul it would be hardmasked.
-h
Tim
--
---
Tim Allen [EMAIL PROTECTED
to use EUC-KR
encoding, not UTF-8. Perhaps whatever client you're using to put data
into your database is using that encoding too?
Tim
--
---
Tim Allen [EMAIL PROTECTED]
Proximity Pty Ltd http://www.proximity.com.au
--
---
Tim Allen [EMAIL PROTECTED]
Proximity Pty Ltd http://www.proximity.com.au/
---(end of broadcast)---
TIP 6: explain analyze is your friend
what you want.
Tim
--
---
Tim Allen [EMAIL PROTECTED]
Proximity Pty Ltd http://www.proximity.com.au/
---(end of broadcast)---
TIP 3: Have you checked our extensive FAQ?
http
David Fetter wrote:
== PostgreSQL Weekly News - December 05 2005 ==
Chris Campbell of Big Nerd Ranch shows how to lower a query's priority.
http://weblog.bignerdranch.com/?p=11
I wouldn't normally bother nitpicking news items, but since this is
presumably being held up as expert advice and
--
---
Tim Allen [EMAIL PROTECTED]
Proximity Pty Ltd http://www.proximity.com.au/
---(end of broadcast)---
TIP 9: In versions below 8.0, the planner will ignore your desire to
choose an index scan if your joining column's datatypes do
.
Solutions are to either use UTF-8 as your encoding, or to tell the
database what encoding you really want to use, eg by
set client_encoding to latin1;
to set the encoding that a particular session is going to use.
Tim
--
---
Tim Allen [EMAIL
- must be
very subtle.
regards, tom lane
--
---
Tim Allen [EMAIL PROTECTED]
Proximity Pty Ltd http://www.proximity.com.au/
http://www4.tpg.com.au/users/rita_tim/
---(end of broadcast)---
TIP 9
not hard to then write a script that compares the
current schema version at a site with that expected by the new
application version, and incrementally runs each update script.
Tim
--
---
Tim Allen [EMAIL PROTECTED]
Proximity Pty Ltd http
Tom Lane wrote:
David Wheeler [EMAIL PROTECTED] writes:
bric=3D# reindex index udx_keyword__name;
REINDEX
bric=3D# select * from keyword where name =3D'=BA=CF=C7=D1=C0=C7';
id | name | screen_name | sort_name | active
--++-+---+
1218 |
flow error. Getting warm, it seems, but not there yet. And
there doesn't seem to be a negative equivalent.
Tim
--
-------
Tim Allen [EMAIL PROTECTED]
Proximity Pty Ltd http://www.proximity.com.au/
http://www4.tpg.com.au/users/rita_tim/
ome future version :-).
Tim
--
-------
Tim Allen [EMAIL PROTECTED]
Proximity Pty Ltd http://www.proximity.com.au/
http://www4.tpg.com.au/users/rita_tim/
22 matches
Mail list logo
