Re: [GENERAL] autovacuum process blocks without reporting a deadlock

Thomas Chille escribió: > This are the last log entires for these both processes. Over 9 hours > later, i can see them allready running in the process list : > > 14391 ?S 0:00 postgres: autovacuum process > backoffice_db > 14398 ?S 0:02 postgres: spoon backoffice_db off

Re: [GENERAL] ODBC, access, and joins

=-- On Fri, 11/23/07, Tom Hart <[EMAIL PROTECTED]> wrote: > The problem I'm having is that anything defined as a "text" datatype in > > postgres gets converted to a "memo" datatype in access, and when we > attempt to perform a join query on thatfield access starts complaining > > about not bein

Re: [GENERAL] ODBC, access, and joins

On Fri, Nov 23, 2007 at 03:48:01PM -0500, Tom Hart wrote: > The problem I'm having is that anything defined as a > "text" datatype in postgres gets converted to a "memo" datatype in > access, and when we attempt to perform a join query on that field access > starts complaining about not being ab

[GENERAL] manipulating HeapTuples in a libpq client

I've got a server function that returns a set of HeapTuples. The server function is invoked in a query sent by a libpq client.However, I haven't spotted a way to decompose the HeapTuple returned to the client. Attempts to call GetAttributeByNum on the client result in the linker complaining about a

Re: [GENERAL] autovacuum process blocks without reporting a deadlock

"Thomas Chille" <[EMAIL PROTECTED]> writes: > One Autovacuum process stuck in the middle of the night and it seemed > that it compete with another Select process for an index: > [14391 / 2007-11-21 00:52:14 CET]DEBUG: 0: index > "hst_timerecording_id_timerecording_idx" now contains 8537 row >

Re: [GENERAL] Primary Key

On: Fri, 23 Nov 2007 09:33:13 +, "Peter Childs" <[EMAIL PROTECTED]> wrote: > The worse thing I meet is people who think primary keys need to be > integer single field unique serial fields > > I tend to agree that primary keys should be single fields if they > need to be referenced but should a

[GENERAL] ODBC, access, and joins

Hi again everybody. I've got kind of a weird one today (the more complicated my db gets, the stranger the questions). I've built a data mine backend to replace our access data mine (eww, I know), but we'd like to still be able to use access to get to the tables, and write queries/reports/etc. a

Re: [GENERAL] best way to handle enum type

Tom Hart wrote: > Ok, that's pretty much what I was told. Our data mine doesn't need to be > aware of other locales/monetary formats atm, but given the changes that are > happening with the datatype, I think I'll just have to stick with > numeric(12,2). Are those TODO items scheduled to be work

Re: [GENERAL] best way to handle enum type

Bruce Momjian wrote: Tom Hart wrote: On a side note, I was just reading through the 8.3 changelog, (where I read about the enum datatype) and I noticed this line * Widen the MONEY data type to 64 bits (D'Arcy Cain) This greatly increases the range of supported MONEY values

Re: [GENERAL] plpython array support

Sean Davis wrote: > On Nov 19, 2007 9:08 PM, Jorge Godoy <[EMAIL PROTECTED]> wrote: >> Em Monday 19 November 2007 19:29:51 Sean Davis escreveu: >>> Just a simple question--does plpythonu (8.3beta) have support for >>> arrays? I don't see a specific mention of it in the docs, so I >>> suppose not.

[GENERAL] autovacuum process blocks without reporting a deadlock

Hi anybody, I step in just one of our identically customer databases in a kind of a deadlock with Autovacuum involved. One Autovacuum process stuck in the middle of the night and it seemed that it compete with another Select process for an index: [14398 / 2007-11-21 00:52:04 CET]CONTEXT: SQL st

Re: [GENERAL] tsearch2 best practices

Ian Barwick wrote: > 2007/11/18, Mag Gam <[EMAIL PROTECTED]>: >> Hi All, >> >> Planning to implement tsearch2 for my websitem and dbschema. I wanted to >> know if there is a "Best practices" guide I should be following. While >> reading about it, I noticed there were lot of 'gotchas' with this, suc

Re: [GENERAL] Primary Key

On Fri, 2007-11-23 at 11:37 +0100, Martijn van Oosterhout wrote: > On Fri, Nov 23, 2007 at 09:33:13AM +, Peter Childs wrote: > > I tend to agree that primary keys should be single fields if they need to be > > referenced but should also be natural if at all possible. ie use car number > > plate

Re: [GENERAL] [HACKERS] Transaction question

>>> On Fri, Nov 23, 2007 at 5:31 AM, in message <[EMAIL PROTECTED]>, Dragan Zubac <[EMAIL PROTECTED]> wrote: > > Didn't know where to submit question regarding design&performance. This page is the place to figure that out: http://www.postgresql.org/community/lists/ For the questions you h

Re: [GENERAL] best way to handle enum type

Tom Hart wrote: > Tom Hart wrote: > > Peter Eisentraut wrote: > >> Tom Hart wrote: > >> > >>> Hey everybody. I have a field that, in my earlier mySQL days would have > >>> been an enum('q','y','m','c'), and I'm wondering what's the best way to > >>> handle this in pgsql. > >>> > >> > >> If i

Re: [GENERAL] best way to handle enum type

Peter Eisentraut wrote: Tom Hart wrote: Hey everybody. I have a field that, in my earlier mySQL days would have been an enum('q','y','m','c'), and I'm wondering what's the best way to handle this in pgsql. If it's an option, upgrade to 8.3 and use the new enum support. Oops, I think I

[GENERAL] Forming the UK User Group

Interested in helping out with a UK User Group or UK advocacy for PostgreSQL? Then please contact me at [EMAIL PROTECTED] After much discussion about User Groups over last 18 months, its time to get even more active in the UK. Initially, we'd like to recruit a few people to assist with the organis

Re: [GENERAL] Compressed Backup too big

Filip Rembiałkowski wrote: > 2007/11/15, Andrus <[EMAIL PROTECTED]>: >> "PostgreSQL 8.2.3 on i686-pc-mingw32, compiled by GCC gcc.exe (GCC) 3.4.2 >> (mingw-special)" >> Database size in disk returned by pg_database_size() is 210 MB >> >> Database compressesed backup file size is now 125 MB. > >

Re: [GENERAL] Unused item pointers - can someone explain?

On 21/11/2007, Elmer <[EMAIL PROTECTED]> wrote: > > Hello, > > I vacuumed one of my database tables. In vacuum output I saw the > following information about unused item pointers: > > There were 19310 unused item pointers. > > As I understand It means that my table's file consists 19310 free > tupl

Re: [GENERAL] Primary Key

On 21/11/2007, Sascha Bohnenkamp <[EMAIL PROTECTED]> wrote: > > > Fie on you evil synthetic key lovers. Long live the Natural Key! > > think of an foreign key referencing a primary key with 6 columns *urgs* > never! The worse thing I meet is people who think primary keys need to be integer sing

Re: [GENERAL] Requesting for a pgadmin3-1.8.0 RPM for SL4

On Thu, 22 Nov 2007, Kandy Wong wrote: I couldn't build the pgadmin3-1.8.0 from source on SL4. Is there any pgadmin3 verion 1.8.0 RPMs available for SL4 or RHEL4? I've found a link for a beta3 version: http://www.postgresql.org/ftp/pgadmin3/release/v1.8.0-beta3/rhel-4/rpms/ But the contents are

Re: [GENERAL] Primary Key

On Fri, Nov 23, 2007 at 09:33:13AM +, Peter Childs wrote: > I tend to agree that primary keys should be single fields if they need to be > referenced but should also be natural if at all possible. ie use car number > plates rather than some serial int. Car number plates are unique over time? I

[GENERAL] Transaction question

Hello all Didn't know where to submit question regarding design&performance. Here's the situation. Basically process will take one message at a time,send it and the will send another one,each process knows which message to take from the table based on provider value. First situation: table

Re: [GENERAL] Primary Key

On Fri, Nov 23, 2007 at 12:00:18PM +0100, Csaba Nagy wrote: > I'm not sure how it is in the US, but here in Germany I just reused a > car plate from the owner it had before me... so now the plate is > uniquely associated at most with the car, not the owner... and I'm > pretty sure that's not unique

Re: [GENERAL] autovacuum process blocks without reporting a deadlock

i have to wait till monday, then i can provide these lines. thanks, thomas On Nov 23, 2007 1:32 PM, Alvaro Herrera <[EMAIL PROTECTED]> wrote: > Thomas Chille escribió: > > > This are the last log entires for these both processes. Over 9 hours > > later, i can see them allready running in the pro

Re: [GENERAL] Primary Key

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 11/23/07 03:33, Peter Childs wrote: > > > On 21/11/2007, *Sascha Bohnenkamp* <[EMAIL PROTECTED] > > wrote: > > > Fie on you evil synthetic key lovers. Long live the Natural Key! > > think of an foreign key refe

Re: [HACKERS] [GENERAL] AutoVacuum Behaviour Question

Tom Lane wrote: > Alvaro Herrera <[EMAIL PROTECTED]> writes: > No, it isn't. Please add a TODO item about it: > * Prevent long-lived temp tables from causing frozen-Xid advancement > starvation > >> > > Jeff Amiel wrote: > >> Can somebody explain this one to me? because of our aud

Re: [GENERAL] Primary Key

Ron Johnson <[EMAIL PROTECTED]> writes: > On 11/23/07 03:33, Peter Childs wrote: >> The worse thing I meet is people who think primary keys need to be >> integer single field unique serial fields >> >> I tend to agree that primary keys should be single fields if they need >> to be referenced but s

Re: [GENERAL] best way to handle enum type

Tom Hart wrote: Peter Eisentraut wrote: Tom Hart wrote: Hey everybody. I have a field that, in my earlier mySQL days would have been an enum('q','y','m','c'), and I'm wondering what's the best way to handle this in pgsql. If it's an option, upgrade to 8.3 and use the new enum support.

Re: [GENERAL] Primary Key

On Nov 23, 2007, at 17:35 , James B. Byrne wrote: Why is this desire not better satisfied by an index rather than a key? What's your distinction between an index and a key? For what it's worth, both UNIQUE and PRIMARY KEY constrain a column (or set of columns) to be unique, or a key in th