Hello.
I have two bases one in char set win1251 another in koi8-r, locale in
koi8-r.
The question is, what do I need to be made that right sort (by alphabet)
in base with the char set win1251.
Sorry for my English.
---(end of broadcast)---
T
My mistake i faced this problem below.
is it taken care in 7.4dev ?
the problem has no significance in real
world though.
Regds
mallah.
tradein_clients=# SELECT * from t_a;
userid | username
+---
105989 | afri4ta
105557 | koreantraders
89773 | NQChinh
89800 | ynd
I have a problem partly caused by stupidity, which I desperately need to
fix if at all possible. Me and a colleague have tried fixing it and
may've made it worse...
I have a reasonably big db (21GB on disk, fully vaccuumed). I upgraded
from 7.3.2 to 7.3.3, forgetting to shut it down cleanly first.
On Fri, 27 Jun 2003, Rajesh Kumar Mallah wrote:
> My mistake i faced this problem below.
> is it taken care in 7.4dev ?
In 7.4 I get
"ERROR: Infinite recursion detected in rules for relation t_b"
> tradein_clients=# CREATE VIEW t_b AS SELECT * from t_a;
> CREATE VIEW
> tradein_clients=# CREATE
Sam Barnett-Cormack <[EMAIL PROTECTED]> writes:
> [ accidentally clobbered pg_control ]
It sounds like the main problem is too small a value in the XID
(transaction ID) counter, so that all your data tuples appear to be in
the future. pg_resetxlog has an option to force an initial XID but
you nee
Late as it is, I'll try this monday. I hope it works, other suggestions
still welcome of course, thanks very much.
On Fri, 27 Jun 2003, Tom Lane wrote:
> Sam Barnett-Cormack <[EMAIL PROTECTED]> writes:
> > [ accidentally clobbered pg_control ]
>
> It sounds like the main problem is too small a va
What could cause a table to act serialized when read committed transactions
are set in the configuration? That is something I am running into, which
provoked my [incorrect] example.
From: "Bruno Wolff III" <[EMAIL PROTECTED]>
Sent: Thursday, June 26, 2003 4:30 PM
> On Thu, Jun 26, 2003 at 14:00:3
Hi Folks,
I'd like to be able to support both Japanese and English character sets
in the same database if possible. First off, is this possible, or are
there some restrictions (such as specific tables need to have specific
character sets only).
I think this is a case of Multi-Byte Support. If thi
> I'd like to be able to support both Japanese and English character
> sets in the same database if possible. First off, is this possible,
> or are there some restrictions (such as specific tables need to have
> specific character sets only).
>
> I think this is a case of Multi-Byte Support. If thi
On Fri, Jun 27, 2003 at 02:18:52AM +0200, Mendola Gaetano wrote:
> I heard only about the point in time recovery in version 7.4, that's all,
> what about, for example, a "multi DB/HOST select" or the nested transactions ?
multiple-host-queries ?!
wow - what did you have smoked ? ;-)
cu
--
I just saw someone mention SQLRelay on the postfix-users mailing list, and it
seems like a really cool project. I haven't heard of it though (which is
kind of surprising, since I've been looking for something like this for a
while) so I wanted to see if anyone here has any experience with it.
On Fri, 27 Jun 2003 [EMAIL PROTECTED] wrote:
> On Fri, Jun 27, 2003 at 02:18:52AM +0200, Mendola Gaetano wrote:
>
>
> > I heard only about the point in time recovery in version 7.4, that's all,
> > what about, for example, a "multi DB/HOST select" or the nested transactions ?
> multiple-host-que
All,
i got the answer i was needing. I used the following:
select max(id) from table
it works great!! :)
--- Josh Goldberg <[EMAIL PROTECTED]> wrote:
> What could cause a table to act serialized when read
> committed transactions
> are set in the configuration? That is something I
> am runnin
Note that that has race conditions, i.e. two clients operating at the same
time could get the same max(id).
The setval currval and nextval functions exist to prevent race conditions,
and they work well. Rolling your own is a recipe for disaster.
On Fri, 27 Jun 2003, Michael Kovalcik wrote:
>
Hi all,
using pg_dump I get the following error message:
pg_dump stats > stats.sql
pg_dump: ERROR: cannot read block 1055 of summary: Input/output error
pg_dump: lost synchronization with server, resetting connection
pg_dump: SQL command to dump the contents of table "summary" failed:
PQendcopy
how do i get support for latin character on my psql
console
:-) Sidar Lopez Cruz- Cero Riesgo,
S.A.
On Fri, Jun 27, 2003 at 10:06:41 -0700,
Josh Goldberg <[EMAIL PROTECTED]> wrote:
> What could cause a table to act serialized when read committed transactions
> are set in the configuration? That is something I am running into, which
> provoked my [incorrect] example.
Getting lucky. Did you act
some searches on this have produced mixed results...
do we have a stable means to replicate transactions between two physical
servers, preferrably in master - master configuration where updates/inserts can
be done on either database and the results replicated to the other master.
Dave
---
>> I just tried a fresh install of pg 7.3.1 on a SuSE
8.1 box. I keep getting
>> messages like
>> Failed to initialize lc_messages to ''
>> during initdb. I already tried --locale=C but no
help. Anyone any
>> ideas?
>Try initdb with -d option and show us the (last few
lines of) output.
>Also, what
Dimitri Nagiev <[EMAIL PROTECTED]> writes:
> using pg_dump I get the following error message:
> pg_dump: ERROR: cannot read block 1055 of summary: Input/output error
> calls from psql give me similar trouble:
> ERROR: cannot read block 1055 of summary: Interrupted system call
> There's a good ba
20 matches
Mail list logo
