Bohdan KRAVCHUK wrote:
> Hello:
Hi, there,
> Is there anyone who runs postgresql on win32 platform? If so, i would wish
> very much to get in touch with that person.
>
> The reason, I need help with installing postgres. I tried compiling both
> by VC++ and sygwin - both times unsuccessfully.
>
Hello:
Is there anyone who runs postgresql on win32 platform? If so, i would wish
very much to get in touch with that person.
The reason, I need help with installing postgres. I tried compiling both
by VC++ and sygwin - both times unsuccessfully.
Somebody more successful than me, please turn u
> As a note, the RedHat init scripts shipped with the RPM's are not
> intended for 'special' applications such as this one -- however, I am
> working on a more generalized setup in the RPM's where multiple
> postmasters, etc, could be started.
Yup. I had to do slightly more than trivial mods to
Karl DeBisschop wrote:
>
> > Yes you can. Use a postmaster parameter to specify a different port
> > number, and use that port number in your connections.
>
> What I was missing was that:
>
>rm -f /tmp/.s.PGSQL.* > /dev/null
>
> must be removed from thr redhat init script
> Yes you can. Use a postmaster parameter to specify a different port
> number, and use that port number in your connections.
What I was missing was that:
rm -f /tmp/.s.PGSQL.* > /dev/null
must be removed from thr redhat init script in order for the sockcts
to work correct
> From: Bruce Momjian <[EMAIL PROTECTED]>
>
> KD> About 2 weeks ago, I reported a problem with 6.5.3 on Linux version
> KD> 2.2.7-1.23smp (VA-Research). Basically, we have one gigabyte scale
> KD> table that will not index on the text field, although it does index on
> KD> a char(1) an
>
> About 2 weeks ago, I reported a problem with 6.5.3 on Linux version
> 2.2.7-1.23smp (VA-Research). Basically, we have one gigabyte scale
> table that will not index on the text field, although it does index on
> a char(1) and a date field.
Sorry, I don't remember this.
>
> We been unabl
About 2 weeks ago, I reported a problem with 6.5.3 on Linux version
2.2.7-1.23smp (VA-Research). Basically, we have one gigabyte scale
table that will not index on the text field, although it does index on
a char(1) and a date field.
We been unable to find the cause of the problem ourselves,
[Charset iso-8859-1 unsupported, filtering to ASCII...]
> Can somebody translate this error to english for me :)
>
> ERROR: RestrictionClauseSelectivity: bad value 2.451276
>
> I'm getting it whenever I try to run an update query through ODBC.. any
> ideas?
My guess is you are running Alpha and
[Charset ISO-8859-1 unsupported, filtering to ASCII...]
>
> I got an error like this after use alter table to add a column
>
> when I do a select I got this:
>
>
> database=> select * from table where column = 1;
> ERROR: RestrictionClauseSelectivity: bad value 2.452260
>
> but if i do :
>
I got an error like this after use alter table to add a column
when I do a select I got this:
database=> select * from table where column = 1;
ERROR: RestrictionClauseSelectivity: bad value 2.452260
but if i do :
select * from table where column > 1;
it goes ok.
strange...
On Mon, 3 Jan
Can somebody translate this error to english for me :)
ERROR: RestrictionClauseSelectivity: bad value 2.451276
I'm getting it whenever I try to run an update query through ODBC.. any
ideas?
Thanks,
Ted Wallingford
12 matches
Mail list logo
