Re: [GENERAL] Relative performance of prefix and suffix string matching

Le 23/09/2011 12:30, Alban Hertroys a écrit : > On 23 September 2011 11:47, Andrew Rose > wrote: > > Basic Question: In text fields, is prefix matching significantly faster > than suffix matching? > > > It does depend on what type of index you use. BTr

Re: [GENERAL] [ANNOUNCE] PostgreSQL Core Team

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Le 27/04/2011 20:48, Dave Page a écrit : > I'm pleased to announce that effective immediately, Magnus Hagander > will be joining the PostgreSQL Core Team. > > Magnus has been a contributor to PostgreSQL for over 12 years, and > played a major part in

Re: [GENERAL] tgname munged

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Le 04/08/2010 17:30, gnuo...@rcn.com a écrit : > Can anyone explain why the following query (used by AQT to display its tree): > > SELECT trig.tgname, > tab.relname, > case trig.tgenabled > when '1' then 'yes' > else 'no' > end, > trig.oid > FROM pg_c

Re: [GENERAL] Preventing a user to use implicit casts

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Scott Marlowe a écrit : > On Wed, Jul 1, 2009 at 11:57 AM, "Stéphane A. > Schildknecht" wrote: >> Problem yet is I can't use slony any more to replicate data, as it falls in > >> I'm quit disappointed, as

[GENERAL] Preventing a user to use implicit casts

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi, Is there a way to define some implicit casts so that only one specific database user can use them, and they're not visible to others? I'm facing the case where to have same behaviour as in 8.2 for this "Non-character data types are no longer auto

Re: [GENERAL] Using xmin to identify last modified rows

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Gregory Stark a écrit : > "Stéphane A. Schildknecht" writes: (...) > > You could order by age(xmin) instead > >> What would be the best way to get last modified rows? > > I'm not sure using xmin is such a g

[GENERAL] Using xmin to identify last modified rows

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi, Trying to identify last modified (updated or inserted) rows in a table, I thought I could use xmin. I tried is to get some lines sorted by xmin. When doing it on a slonified database, I had no problem getting these lines. But, trying the same q

Re: [GENERAL] Trigger before delete does fire before, but delete doesn't not happen

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Tom Lane a écrit : > Adrian Klaver <[EMAIL PROTECTED]> writes: >> Thanks for the explanation. Just so I am clear,the act of updating the row >> in p_commandeligne_ad creates a new tuple for the row with id of 1. This >> means the original statement "

Re: [GENERAL] Trigger before delete does fire before, but delete doesn't not happen

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Adrian Klaver a écrit : > On Friday 28 November 2008 3:47:10 am Stéphane A. Schildknecht wrote: >> drop table commande cascade; >> drop table commandeligne; >> >> CREATE TABLE commande >> ( >> id integer NOT N

[GENERAL] Trigger before delete does fire before, but delete doesn't not happen

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi, I'm faced with something like a comprehension problem. The exemple may be oversimplified, but, it seems same problem happens with updates. To simplify, I have triggers on 2 tables (commande and commandeligne). When deleting from table commande,