Re: [GENERAL] MySQL search query is not executing in Postgres DB

2012-02-18 Thread premanand
Hi Marti,

Thanks for your reply. It works as expected. 

Regards,
Prem

--
View this message in context: 
http://postgresql.1045698.n5.nabble.com/MySQL-search-query-is-not-executing-in-Postgres-DB-tp5492402p5494971.html
Sent from the PostgreSQL - general mailing list archive at Nabble.com.

-- 
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-general


[GENERAL] Question on Rules

2012-02-18 Thread mgould
I am creating a rule which will copy a record when it is changed to a
audittable.  My question is that the first column is a UUID data type
with a defined as auditaccessorid uuid DEFAULT
isscontrib.uuid_generate_v4() NOT NULL,

Right now I've got that set to NULL to allow the parser to "compile". 
What value should I have in here since I want a newly created UUID?

CREATE RULE log_accessor AS ON UPDATE TO iss.accessor
WHERE NEW.* <> OLD.*
DO INSERT INTO iss.auditaccessor VALUES (NULL,
  'C',
  new.loaddtlid, 
  new.seqno, 
  new.billable,
  new.payind,
  new.code,
  new.description, 
  new.ref,
  new.tractororcarrierflag, 
  new.tractororcarrierno,
  new.tractorpct,
  new.charge,
  new.type,
  new.checkdate,
  new.checkno,
  new.processed,
  new.itemflag, 
  new.tractortermloc,
  new.cost,
  new.batchno,
  new.editdatetime,  
  new.edituser);

Best Regards,
 
Michael Gould
Intermodal Software Solutions, LLC
904-226-0978


-- 
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-general


[GENERAL] Full text search ranking: ordering using index and proximiti ranking with OR queries

2012-02-18 Thread Andrey Chursin
Hello

I have two unrelated questions about fts function ts_rank:

1) I've created GiST index on column with fts vector, but query
SELECT * FROM table ORDER BY ts_rank(field, :query) LIMIT 20
is perfomed with sequential table scan. Index was created on field
column. Does it mean FTS indexes does not support order by ranking? Or
I need somehow to create separated index for ranking?

2) I have a misunderstanding with proximity ranking work. Given two
vectors 'a:1 b:2' and 'a:1 b:1000', i am measuring ts_rank(vector, 'a'
| 'b'). And it is equal! But when i am replacing query with &
operator, e.g. asking for ts_rank(vector, 'a' & 'b') i am getting
different numbers. Why do I get proximity ranking only for AND fts
queries? This is a problem as far as to_tsquery produces OR queries,
so i need self-written postprocessing of query to replace OR with AND.

-- 
Regards,
Andrey

-- 
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-general


Re: [GENERAL] Pokey Fedora Updates for Postgresql?

2012-02-18 Thread Jerry Levan

On Feb 17, 2012, at 4:58 PM, Tom Lane wrote:

> Jerry Levan  writes:
>> On Feb 17, 2012, at 4:21 PM, Tom Lane wrote:
>>> I beg your pardon?
> 
>> Sorry, they do not appear in *my* 'yum update' or yumex or the software 
>> update program.
> 
> Huh.  Something broken on your end, but what?  The only thing that looks
> funny to me in your output is
> 
>> [jerry@bigbox ~]$ yum check-update
>> Loaded plugins: fastestmirror, presto, refresh-packagekit
>  ^
> 
> That's not a standard plugin (leastwise I don't see it when I run yum)
> so I'm wondering if it's pointing you to a dysfunctional mirror.  Try
> disabling it.
> 
> FWIW, as of today I see this on my F16 machine:
> 
> [tgl@rh3 ~]$ sudo yum check-update
> Loaded plugins: auto-update-debuginfo, langpacks, presto, refresh-packagekit
> updates/metalink |  16 kB 00:00   
>   
> updates  | 4.5 kB 00:00   
>   
> updates/primary_db   | 5.0 MB 00:02   
>   
> updates/group_gz | 431 kB 00:00   
>   
> updates-debuginfo/metalink   |  13 kB 00:00   
>   
> updates-debuginfo| 3.1 kB 00:00   
>   
> updates-debuginfo/primary_db | 391 kB 00:00   
>   
> 
> The fact that your "updates/primary_db" is smaller than mine seems
> pretty suspicious.  I wonder whether you've been seeing any Fedora
> updates at all lately?  Maybe everything you've updated has been coming
> from those non-Fedora repos.
> 
>   regards, tom lane

Sigh, "Whenever the unlikely solutions are rejected then all that are left are 
the probable."

In fedora 15 I had been using Devrim's repo and had 'excluded' postgresql in 
the fedora
and fedora update repositories.

When fedora 16 came out I removed the exclusion from the fedora repo but NOT 
the update repo.
(and I disabled the pgdg repo).

Sorry for all the noise…

Jerry
-- 
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-general


[GENERAL] autovacuum and deadlocks

2012-02-18 Thread Gregg Jaskiewicz
What is a likelihood of a deadlock occurring, caused (or helped by)
auto vacuum.
This is on 8.3.

The table with deadlocks was quite busy with updates, etc.

-- 
GJ

-- 
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-general


Re: [GENERAL] autovacuum and deadlocks

2012-02-18 Thread Scott Marlowe
On Sat, Feb 18, 2012 at 8:59 AM, Gregg Jaskiewicz  wrote:
> What is a likelihood of a deadlock occurring, caused (or helped by)
> auto vacuum.
> This is on 8.3.
>
> The table with deadlocks was quite busy with updates, etc.

The only locking issues (not deadlocks) I've ever had with autovacuum
were priority inversion issues with slony, where a slony execute
script was stuck behind an autovacuum, and something else was then
stuck behind the slony execute script.

I'm afraid we'll need more info to determine what was happening.  It's
a good idea to make a snapshot of what's in pg_stat_activity and
pg_locks when these things happen so you have something to look at
after the fact.

-- 
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-general


Re: [GENERAL] MySQL search query is not executing in Postgres DB

2012-02-18 Thread Susanne Ebrecht

Am 17.02.2012 17:24, schrieb Alban Hertroys:

On 17 February 2012 17:19, Scott Marlowe

Have you tried casting to varchar(1000) or something like that?

Don't MySQL's varchars only go to 255? That's why every MySQL database
uses blobs for text data, isn't it?



Yes.

--
Dipl. Inf. Susanne Ebrecht - 2ndQuadrant
PostgreSQL Development, 24x7 Support, Training and Services
www.2ndQuadrant.com


--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-general


Re: [GENERAL] MySQL search query is not executing in Postgres DB

2012-02-18 Thread Daniel Neugebauer
On 02/19/2012 12:05 AM, Susanne Ebrecht wrote:
> Am 17.02.2012 17:24, schrieb Alban Hertroys:
>> On 17 February 2012 17:19, Scott Marlowe
>>> Have you tried casting to varchar(1000) or something like that?
>> Don't MySQL's varchars only go to 255? That's why every MySQL database
>> uses blobs for text data, isn't it?
>>
> 
> Yes.

Slightly off-topic but MySQL actually changed that behaviour in bugfix
release 5.0.3 according to their manual. I was surprised myself when a
colleague of mine used varchar(500) last week. Their upper limit is now
at 2^16-1 = 65535 bytes. I don't have a much advanced knowledge in DB
matters yet, but I usually decided for TEXT or MEDIUMTEXT types in MySQL
when I had to store longer text content, IMHO there's no need using
blobs for texts unless you want to keep admin frontends from displaying
the contents right away.

-- 
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-general


Re: [GENERAL] Backup database remotely

2012-02-18 Thread Jasen Betts
On 2012-02-15, Andre Lopes  wrote:
> Hi all,
>
> To do this backup remotely we need to open the 5434 port in the Firewall?

Yes, you need a connection to the database,  opening the firewall is
the simplest way to get that.  (other ways include VPN and ssh 
tunneling)

>> pg_dump -h  (or pg_dumpall)

-- 
⚂⚃ 100% natural


-- 
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-general