On Jun 10, 2014, at 8:26 AM, Vick Khera wrote:
Thanks so much for this.
We do a lot of searching on this column, so pre-computing seems to be the way.
I'm not worried about disk space for now, and can revisit that later if there
is a problem
Just for clarification on this:
Option A (less fas
Vick Khera wrote:
> Jonathan Vanasco wrote:
> Personally in these days of cheap disks I'd go with the dedicated
> column. Given that, you want to just have a GIN index on that one
> column, and the query you want, given some plain text string like
> "fluffy dog" is this:
>
> select plainto_tsqu
On Mon, Jun 9, 2014 at 8:55 PM, Jonathan Vanasco wrote:
> I can't figure out which one to use. This is on a steadily growing
> table of around 20MM rows that gets 20-80k new records a day, but existing
> records are rarely updated.
The question as always is a time-space trade-off. How
I'm having some issues with fulltext searching.
I've gone though the list archives and stack overflow, but can't seem to get
the exact answers. hoping someone can help.
Thanks in advance and apologies for these questions being rather basic. I just
felt the docs and some online posts are lea
On Saturday 02 May 2009 13:08, Daniel Verite wrote:
>Terry Lee Tucker writes
>
> > Q1: Can we set up a scenario where there is more that one
> > warm standby?
>
> Yes. But you'll have to consider what you want to happen when one
> standby is correctly receiving the WAL files and another is
Terry Lee Tucker writes
Q1: Can we set up a scenario where there is more that one
warm standby?
Yes. But you'll have to consider what you want to happen when one
standby is correctly receiving the WAL files and another is not,
because the archive_command has to either fail or succee
Greetings:
We are researching implementing a warm backup solution for our existing
databases. We have a two node cluster running RH which are connected to a
SAN. There is a total of 11 database clusters with the two node linux cluster
balancing the load. At the moment, we are not doing any WAL
On Fri, 22 Oct 2004 14:18:52 -0400, Jan Wieck <[EMAIL PROTECTED]> wrote:
>
>
> That "multiple hosts" sounds that he came across the NDB cluster stuff
> that will become available in MySQL someday. Be aware that this new
> table handler will to my knowledge NOT support foreign keys. So the
> enfor
On 10/21/2004 3:40 PM, John Wells wrote:
Guys,
My boss has been keeping himself busy reading MySQL marketing pubs,
and came at me with a few questions this morning regarding PostgreSQL
features (we're currently moving to PostgreSQL).
While I don't think either are really that important for our
situ
On Thu, Oct 21, 2004 at 03:40:23PM -0400, John Wells wrote:
> Guys,
>
> My boss has been keeping himself busy reading MySQL marketing pubs,
> and came at me with a few questions this morning regarding PostgreSQL
> features (we're currently moving to PostgreSQL).
I should point out that there's a
PROTECTED]>
ge.net>cc: "[EMAIL PROTECTED]"
<[EMAIL PROTECTED]>
Sent by: Subject: Re: [GENERAL] Two
questions from the boss (SQL:2003 && scalability
> and what sort of capabilities PostgreSQL has to scale across
> > multiple CPUs and hosts (multithreading, load balancing, etc).
> >
>
> Well, PostgreSQL can certainly take advantage of multiple CPU's,
> although there are some cases where we could do more (use multiple CPU
> on one query). You
On 21 Oct 2004, Robert Treat wrote:
> slony to set up load balancing depending on your needs... though I
> should say that PostgreSQL has tremendous ability to scale up even
> without getting into all the buzzword friendly schemes.
You should strive to pool your connections, though. Of course, t
On Thu, 2004-10-21 at 15:40, John Wells wrote:
> Guys,
>
> My boss has been keeping himself busy reading MySQL marketing pubs,
> and came at me with a few questions this morning regarding PostgreSQL
> features (we're currently moving to PostgreSQL).
>
I'd be interested to see what my$ql has to s
Guys,
My boss has been keeping himself busy reading MySQL marketing pubs,
and came at me with a few questions this morning regarding PostgreSQL
features (we're currently moving to PostgreSQL).
While I don't think either are really that important for our
situation, he wanted to know specifically w
Hello,
Two questions today:
1. In my ongoing quest to document Ultradev vs Postgresql =:-D I am
running into a problem that seems to be SQL related. As you may imagine
the code generated by Ultradev is not perfect...
My SELECT request gets passed like this
resultat.jsp?mnuAct=--&entName=BOUL&
> > 1. How do you remove one of two identical rows
> > from a pgsql table ?
>
> DELETE FROM t1 WHERE wil do the stuff for you. If you don't know
> the value into the duplicate field just export the database with pg_dump
> create
> a unique index onto this field and reimport all your data. Du
Well maybe now is a good time to take a look at your
design and see why you have to do this.
There just happens to be a number of great DBAs on
this list as well. :-)
Rudy
On 6 Aug 99, at 2:14, Roberto Moreda wrote:
> Sorry for being so reiterative :)
>
> The planifier isn't perfect for many q
Sorry for being so reiterative :)
The planifier isn't perfect for many queries...
Is there any way (without touch C code) to tell explicitly the plan of a query
to Postgres?
How can I manage the problem of select a few rows with a boolean atribute
when they are 5 rows in a table of 10 rows?
Hello all,
I have two questions about PostgreSQL 6.5:
1. CLUSTER does not work on indexes with more than one field. Is this
correct?
2. In the distribution tarball, the top-level directory is
"postgresl-6.5". Isn't there a 'q' missing?
--
Christian Ullrich
20 matches
Mail list logo