Harshad Pethe wrote:
> I have recently tried to install pgsql on Windows but
> I get the following error consistently !
>
> Error : " psql : recieved invalid response to SSL negotiation ! "
>
> This error is encountered as soon as I try to start psql !
Sounds like an SSL problem.
Chec
Glyn Astill wrote:
http://privatepaste.com/cbY2S4JhtA
Very little difference with the -O0
FWIW: there also seems to be a fairly indepth discussion on the cobalt
related netbsd list from last year about a problem that looks very
similiar (at least to you issue with etch):
http://www.nabble
Finally figured out what was wrong. The data folder had incorrect
permissions after unzipping the base backup. For me, the solution was
unchecking the "Inherit from parent the permission entries that apply to
child objects" option in the Advanced Security Settings dialog for the
data folder & g
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi, I was reading the Wikipedia entry on GiST (http://
en.wikipedia.org/wiki/GiST) and it mentions
"""
Although originally designed for answering Boolean selection queries,
GiST can also support nearest-neighbor search, and various forms of
sta
On Tue, Aug 5, 2008 at 6:53 PM, Tom Lane <[EMAIL PROTECTED]> wrote:
>
> There's support for prefix text search in CVS HEAD, but not in any
> released version ...
>
>regards, tom lane
>
Oh, does that mean it won't be released until 8.4?
Glyn Astill <[EMAIL PROTECTED]> writes:
>> What replaces the VARATT_SIZEP macro in version 8.3? I have spent a
>> long time checking the documentation and have not found the answer.
> SET_VARSIZE
Yes; you should always use VARSIZE() to fetch the length and
SET_VARSIZE() to set it. If you need yo
Sim Zacks <[EMAIL PROTECTED]> writes:
> Results below:
>> ... but given that, I wonder whether the cost isn't from fetching
>> the toasted messageblk data, and nothing directly to do with either
>> the encode() call or the ~~ test. It would be interesting to compare
>> the results of
Okay, so sub
Hi,
i´m trying to do a trigger that its called when update or insert, that
update the tsvectors, for text-search. Here´s my code:
create table x(
cod serial,
texto text,
vectors tsvector,
constraint pk primary key(cod)
);
CREATE OR REPLACE FUNCTION atualiza_vectors() RETURNS trigger AS $$
>
> What replaces the VARATT_SIZEP macro in version 8.3? I have
> spent a long
> time checking the documentation and have not found the
> answer.
>
SET_VARSIZE
__
Not happy with your email address?.
Get the one you really want - m
On 8/5/08, Don Pannese <[EMAIL PROTECTED]> wrote:
>
> I have C code which defines some user defined postgres functions. This code
> has been used with Postgres version 7.4 and it uses the VARATT_SIZEP macro.
>
seems that macro was deprecated in 8.3... this is the commit that removed it:
http://arc
On Tue, Aug 05, 2008 at 06:03:19AM +0200, Henry wrote:
> just much simpler to use -- not as flexible and as powerful as Slony, but
> if all you need to do is replicate some tables with minimum fuss and
> without having to learn a new language, then Skytools (based on my
> personal experience with
http://privatepaste.com/cbY2S4JhtA
Very little difference with the -O0
__
Not happy with your email address?.
Get the one you really want - millions of new email addresses available now at
Yahoo! http://uk.docs.yahoo.com/ymail/new.ht
Hello all,
I have C code which defines some user defined postgres functions. This
code has been used with Postgres version 7.4 and it uses the
VARATT_SIZEP macro.
I updated to Postgres version 8.3 and attempted to compile my C code and
noticed that the VARATT_SIZEP macro (which my code use
Hi,
Is Heikki's Visibility Map patch included for the Postgresql 8.4 version
http://archives.postgresql.org/pgsql-hackers/2007-11/msg00142.php
If not whats the status of that patch? Im especially interested in the
index-only scan mentioned there!!!
Thanks
On Tue, Aug 5, 2008 at 12:45 PM, Bayless Kirtley <[EMAIL PROTECTED]> wrote:
> I had to move my database to a new disk. I dropped the original after a
> pg_dump and then removed the old directory. I then ran initdb on the new
> location, created the database and restored from the pg_dump.
>
> My pro
Bayless Kirtley wrote:
I had to move my database to a new disk. I dropped the original after
a pg_dump and then removed the old directory. I then ran initdb on
the new location, created the database and restored from the pg_dump.
My problem now is that I have to supply the full pathnames to sta
I had to move my database to a new disk. I dropped the original after a pg_dump
and then removed the old directory. I then ran initdb on the new location,
created the database and restored from the pg_dump.
My problem now is that I have to supply the full pathnames to start or stop the
server.
Hi,
I have recently tried to install pgsql on Windows but I get the
following error consistently !
Error : " psql : recieved invalid response to SSL negotiation ! "
This error is encountered as soon as I try to start psql ! The installation
completes fine , but I'm not able to do anythin
In response to "Kynn Jones" <[EMAIL PROTECTED]>:
> Hi. I have a database that is created and populated by a Perl script.
> (FWIW, the size of this database is about 12GB, according to
> pg_database_size()).
>
> If, right after the database is built, I connect to it and manually run
> VACUUM ANA
Hi. I have a database that is created and populated by a Perl script.
(FWIW, the size of this database is about 12GB, according to
pg_database_size()).
If, right after the database is built, I connect to it and manually run
VACUUM ANALYZE, I get the warning
NOTICE: max_fsm_relations(1000) equa
"Matthew T. O'Connor" <[EMAIL PROTECTED]> writes:
> Tom Lane wrote:
>> 8.2. But you could still get that message, even in CVS HEAD, if
>> autovacuum was failing to complete for some reason (and had been
>> failing for quite a long time).
> Should that message to updated since a database-wide vacu
Tom Lane wrote:
"Matthew T. O'Connor" <[EMAIL PROTECTED]> writes:
BTW, what version of PostgreSQL is this? Database-wide vacuum is no
longer required for XID wraparound issues. I think this was an 8.3
change but might have happened in 8.2, I don't remember.
8.2. But you could still get tha
"Matthew T. O'Connor" <[EMAIL PROTECTED]> writes:
>> On Monday 04 August 2008 11:04:00 pm Robert Shaw wrote:
>>> "WARNING: database "mydb" must be vacuumed within 177009986 transactions
>>> HINT: To avoid a database shutdown, execute a full-database VACUUM in
>>> "mydb".
> BTW, what version of P
On Tue, Aug 5, 2008 at 7:34 AM, Bill Moran
<[EMAIL PROTECTED]> wrote:
> In response to Jef Peeraer <[EMAIL PROTECTED]>:
>
> You'd probably be best with Slony, just don't replicate that 1 table
> that you'll need to write to.
That's one of my favorite things about slony.
--
Sent via pgsql-general
On Tue, August 5, 2008 9:21 am, Jef Peeraer wrote:
>
> i read about the replication possibilities with postgresql. If i just need
> some replication ( without failover stuff ) to 1 standby server, what
> would be the best option to go with. Slony i presume, although schema
> chanages are not propag
Adrian Klaver wrote:
On Monday 04 August 2008 11:04:00 pm Robert Shaw wrote:
"WARNING: database "mydb" must be vacuumed within 177009986 transactions
HINT: To avoid a database shutdown, execute a full-database VACUUM in
"mydb"."Which is reason I ask the question, is full vacuum backup useful
f
"Vyacheslav Kalinin" <[EMAIL PROTECTED]> writes:
> In our application we need a pattern based text search, that is if user
> supplies 'foo bar' he receives only documents containing words that begin
> with 'foo' or 'bar'
There's support for prefix text search in CVS HEAD, but not in any
released v
tsearch can help you; i have a system with it ... and its ok.
El mar, 05-08-2008 a las 18:03 +0400, Vyacheslav Kalinin escribió:
> Hello,
>
> In our application we need a pattern based text search, that is if
> user supplies 'foo bar' he receives only documents containing words
> that begin with
Hello,
In our application we need a pattern based text search, that is if user
supplies 'foo bar' he receives only documents containing words that begin
with 'foo' or 'bar', including themselves (something similar to MySQL '+foo*
+bar*' text search query). Currently we use separate table for uniqu
Gregory Stark <[EMAIL PROTECTED]> writes:
> "Tom Lane" <[EMAIL PROTECTED]> writes:
>> The trouble with that approach is that it overrides *everything* that
>> configure would normally put into CFLAGS. I only want one thing
>> changing, please ... this is confusing enough already.
> Eh?
Sorry, me
In response to Jef Peeraer <[EMAIL PROTECTED]>:
>
> On Tue, 5 Aug 2008, Bill Moran wrote:
>
> > In response to Jef Peeraer <[EMAIL PROTECTED]>:
> > >
> > > i read about the replication possibilities with postgresql. If i just
> > > need
> > > some replication ( without failover stuff ) to 1 st
On Monday 04 August 2008 11:04:00 pm Robert Shaw wrote:
> Hi,
>
> I've been trying to get to the bottom of the differences between a vacuum
> and a vacuum full, it seems to me that the difference is that a vacuum full
> also recovers disk space(and locks things making it less than useful on
> produ
On Tue, 5 Aug 2008, Bill Moran wrote:
> In response to Jef Peeraer <[EMAIL PROTECTED]>:
> >
> > i read about the replication possibilities with postgresql. If i just need
> > some replication ( without failover stuff ) to 1 standby server, what
> > would be the best option to go with.
>
> Yo
In response to Jef Peeraer <[EMAIL PROTECTED]>:
>
> i read about the replication possibilities with postgresql. If i just need
> some replication ( without failover stuff ) to 1 standby server, what
> would be the best option to go with.
Your description of you requirements is very lacking, so
On Mon, Aug 04, 2008 at 05:00:31PM -0400, Rajarshi Guha wrote:
> On Aug 4, 2008, at 4:55 PM, Francisco Reyes wrote:
> > select a.cid as ac, b.cid as bc, count(*) from aic_cid a left
> >outer join
> >aic_cid b on a.cid <>b.cid and a.id = b.id where b.cid is not null
> >group by
> >a.cid, b.cid o
On 05/08/2008 08:21, Jef Peeraer wrote:
would be the best option to go with. Slony i presume, although schema
chanages are not propagated.
Schema changes *are* propagated in Slony, using the EXECUTE SCRIPT
statement:
http://www.slony.info/documentation/stmtddlscript.html
Ray.
---
Is there anything simpler than processing the search_path to obtain
the same effect of
using namespace XXX
or if I'd like to execute the same set of operations on the same
"objects" just in a different schema?
--
Ivan Sergio Borgonovo
http://www.webthatworks.it
--
Sent via pgsql-general mail
"Tom Lane" <[EMAIL PROTECTED]> writes:
> Gregory Stark <[EMAIL PROTECTED]> writes:
>> "Tom Lane" <[EMAIL PROTECTED]> writes:
>>> (Rather than trying to browbeat configure into doing this, I'd suggest
>>> manually adjusting CFLAGS in src/Makefile.global, then "make clean" and
>>> rebuild.)
>
>> eh?
> > "Tom Lane" <[EMAIL PROTECTED]> writes:
> >
> > > (Rather than trying to browbeat configure into
> doing this, I'd suggest
> > > manually adjusting CFLAGS in src/Makefile.global,
> then "make clean" and
> > > rebuild.)
> >
> > eh? either of these should work fine:
> >
> > ./configure --enabl
Hello,
I am a developer working on postgres. I just wrote a function which ll
return a refcurosor as shown below.
CREATE OR REPLACE FUNCTION reffunc(refcursor)
RETURNS refcursor AS
$BODY$
BEGIN
OPEN $1 FOR SELECT * FROM SAM1;
RETURN $1;
END;
$BODY$
LANGUAGE 'plpgsql' VOLATILE
COST
Hi,
I've been trying to get to the bottom of the differences between a vacuum and a
vacuum full, it seems to me that the difference is that a vacuum full also
recovers disk space(and locks things making it less than useful on production
servers). But I believe that both will fix the transacti
i read about the replication possibilities with postgresql. If i just need
some replication ( without failover stuff ) to 1 standby server, what
would be the best option to go with. Slony i presume, although schema
chanages are not propagated.
thanks
jef peeraer
--
Sent via pgsql-general
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
There seems to be a disconnect between the mailing list and the
newsgroup right now. I received a bunch of replies via email that did
not show up in the newsgroup. (I did not receive any messages that were
sent to the mailing list and not to me persona
43 matches
Mail list logo
