In line with my idea of keeping the hackers up to date with stuff in the
IRC channel, here are the topics of the week:
Ah yes, I forgot to add:
* pg_dumpall -Fc option comes up occasionally
Chris
---(end of broadcast)---
TIP 8: explain analyze is you
On Tue, 15 Jun 2004, Tom Lane wrote:
> I wonder though, do the requestors actually know what they're asking for?
> Are they really asking for encoding changes, or are they asking for
> locale changes?
Most people don't know exactly what they want.
A lot of people use SQL_ASCII databases and don'
> -Original Message-
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED] On Behalf Of Tom Lane
> Sent: Tuesday, June 15, 2004 12:04 PM
> To: Peter Eisentraut
> Cc: Christopher Kings-Lynne; Hackers
> Subject: Re: [HACKERS] #postgresql report
>
>
> Pete
Peter Eisentraut <[EMAIL PROTECTED]> writes:
> Christopher Kings-Lynne wrote:
>> * We have a request for how to change database encoding every other
>> day
> This is pretty much impossible. It's analogous to changing, say, the
> endianness of all integers. You would need to rewrite the entire
KL,
> In line with my idea of keeping the hackers up to date with stuff in the
> IRC channel, here are the topics of the week:
You want me & David Fetter should keep a suppliment to this? Since we're on
IRC while you're asleep, usually?
Admittedly, most of the discussion for the last 2 days h
On Tue, 15 Jun 2004, Peter Eisentraut wrote:
Christopher Kings-Lynne wrote:
* We have a request for how to change database encoding every other
day
This is pretty much impossible. It's analogous to changing, say, the
endianness of all integers. You would need to rewrite the entire
database. But
Christopher Kings-Lynne wrote:
> * We have a request for how to change database encoding every other
> day
This is pretty much impossible. It's analogous to changing, say, the
endianness of all integers. You would need to rewrite the entire
database. But pg_dump & restore already does that.
On Tue, 2004-06-15 at 16:05, Jeff wrote:
> Don't forget we get people nearly daily who are encountering problems
> because Debian stable ships with 7.2. We've grown accustomed to giving
> 7.4 (or at least 7.3) advice and often those things don't work on 7.2.
> (such as information_schema and s
* Jeff ([EMAIL PROTECTED]) wrote:
> True enough, however it is still a common topic on the channel.
It's good to let people who are asking know there's an option though.
I'm on the channel too, and do let people know when I see them asking
about it but I'm in 20-odd other channels. :)
> Not every
On Jun 15, 2004, at 11:25 AM, Stephen Frost wrote:
Back-ports of up to 7.4.2 are available for the Debian stable release
at
backports.org.
True enough, however it is still a common topic on the channel.
Not everyone is too keen on using backports either.
Just reporting what I was seeing in the ch
* Jeff ([EMAIL PROTECTED]) wrote:
> Don't forget we get people nearly daily who are encountering problems
> because Debian stable ships with 7.2. We've grown accustomed to giving
> 7.4 (or at least 7.3) advice and often those things don't work on 7.2.
> (such as information_schema and set retu
Don't forget we get people nearly daily who are encountering problems
because Debian stable ships with 7.2. We've grown accustomed to giving
7.4 (or at least 7.3) advice and often those things don't work on 7.2.
(such as information_schema and set returning functions)
Hopefully this will go a
* Christopher Kings-Lynne ([EMAIL PROTECTED]) wrote:
> In line with my idea of keeping the hackers up to date with stuff in the
> IRC channel, here are the topics of the week:
>
> * We have a request for granting on all tables every other day (already
> in TODO)
Hopefully with options to do it
In line with my idea of keeping the hackers up to date with stuff in the
IRC channel, here are the topics of the week:
* We have a request for granting on all tables every other day (already
in TODO)
* We have a request for how to change database encoding every other day
(i suggest a warning
14 matches
Mail list logo
