Hi,
I think I've found what I need to know.
From techdocs.postgresql.org
>> Every you run an INSERT, UPDATE, or DELETE on an indexed table,
PostgreSQL must update all of the table's indexes to reflect the new
data (unlike some
>> RDBMSs, PostgreSQL updates indexes immediately so they never get
Hi,
Say I have a table of 3000 user's,
Before I insert another user I need to check if that user is already in
there, so I have a 3 column index on a table ( phone,lastname,firstname ).
First I check for the user using the index if they are not in there I
then add an new user so I now have 3001
Hello!
"Luis Sousa" <[EMAIL PROTECTED]> wrote in message
[EMAIL PROTECTED]">news:[EMAIL PROTECTED]...
> This is a cryptographically signed message in MIME format.
>
> --ms080209060900030807050408
> Content-Type: text/plain; charset=us-ascii; format=flowed
> Content-Transfer-Encoding: 7
>
> I'm trying to retrieve some info from one column and
> put it in another. I have a column that has a bunch
> of information in it called 'Route'. I don't need to
> show all of that information. Instead I need divide
> that single column into two seperate columns called
> 'Sender' and 'Receiv
On Wed, 27 Nov 2002 09:37:07 -0800, Nathan Young <[EMAIL PROTECTED]>
wrote:
>OK, that works great, but I was told that I should avoid sub-selects when
>possible for performance reasons.
>>
>> select member.memberId, member.name from member left outer join
>> (select * from payment where yearPaid=
