[HACKERS] DROP TABLE and concurrent modifications

2004-02-17 Thread Neil Conway
I can reproduce the following behavior with CVS HEAD. 1. Have a process do INSERTs into a table in a tight loop (I've attached a trivial libpq app that does this) 2. In another session, repeatedly drop and re-create the table that is being modified You should see a stre

Re: [HACKERS] DROP TABLE and concurrent modifications

2004-02-17 Thread Neil Conway
Neil Conway <[EMAIL PROTECTED]> writes: > 1. Have a process do INSERTs into a table in a tight loop (I've > attached a trivial libpq app that does this) Sorry, I was evidently a little too quick off the draw. A simple test app is /really/ attached this time. -Neil #include #include

Re: [HACKERS] DROP TABLE and concurrent modifications

2004-02-17 Thread Tom Lane
Neil Conway <[EMAIL PROTECTED]> writes: > Assuming my analysis is correct, is this a bug? Yes, though a low-priority one in my mind. There is a TODO item about it: * Acquire lock on a relation before building a relcache entry for it (The TODO item is a bit unspecific though, since the issue her

Re: [HACKERS] Renaming tables to other schemas

2004-02-17 Thread Bruce Momjian
Rod Taylor wrote: -- Start of PGP signed section. > On Sun, 2004-02-15 at 01:34, Neil Conway wrote: > > [EMAIL PROTECTED] writes: > > > The capability to move objects to other schemas would be quite > > > useful. > > > > I agree. It's not utterly-trivial to implement (for one thing, you > > need t

Re: [HACKERS] ISAM driver for PostgreSQL

2004-02-17 Thread Bruce Momjian
Merlin Moncure wrote: > Does anybody think there might be some interest in an ISAM driver for > PostgreSQL? I've written a functional alpha that allows PostgreSQL to > be a drop in (or as easy as reasonably possible) replacement for an ISAM > file system driving a COBOL application. It is a STL b

Re: [HACKERS] MS SQL features for new version

2004-02-17 Thread scott.marlowe
On Tue, 10 Feb 2004, Rodrigo wrote: > Shridhar Daithankar wrote: > > Just stumbled upon this. just an FYI, > > > > http://www.microsoft.com/sql/yukon/productinfo/top30features.asp > > > > Shridhar > > From the page: > > > A new Snapshot Isolation (SI) level will be provided at the > > data

[HACKERS] log_line_info

2004-02-17 Thread Andrew Dunstan
Rod Taylor wrote: and I'm willing to entertain other suggestions. Very nice, but you missed the most important. Command Tag. I've had a brief look at this proposal (to allow reporting of the command tag along with username, database, session cookie etc on each log line). I'm wondering wh

Re: [PATCHES] [HACKERS] dollar quoting

2004-02-17 Thread Andrew Dunstan
Tom Lane wrote: Andrew Dunstan <[EMAIL PROTECTED]> writes: andrew=# create table ab$cd$ef (ef$cd$ab text); CREATE TABLE andrew=# \d ab$cd$ef Did not find any relation named "ab$cd$ef". Hmph. I always thought that "$" was only special at the end of a regex, but that doesn't seem to be ho

Re: [HACKERS] log_line_info

2004-02-17 Thread Bruce Momjian
Andrew Dunstan wrote: > Rod Taylor wrote: > > >>and I'm willing to entertain other suggestions. > >> > >> > > > >Very nice, but you missed the most important. Command Tag. > > > > > > I've had a brief look at this proposal (to allow reporting of the > command tag along with username, datab

[HACKERS] Win32 development question

2004-02-17 Thread Dann Corbit
Title: Message I am wanting to fiddle with the latest Win32 stuff, using the Mingw tools. Is it included in the current (2-17-04) snapshot?   I did a download of the tarball and expanded it. I changed directory to the /postgresql-snapshot directory and performed a ./configure   configure: c

[HACKERS] log_line_info plan

2004-02-17 Thread Andrew Dunstan
I am about to redo the patch that would allow tagging of log lines with info via a printf-style string. Current plans are to call the config parameter "log_line_info" and implement the following escapes: %U = user %D = database %T = timestamp %P = pid %L = session log line number %C = sessionid

Re: [HACKERS] log_line_info plan

2004-02-17 Thread Joshua D. Drake
Andrew Dunstan wrote: I am about to redo the patch that would allow tagging of log lines with info via a printf-style string. Current plans are to call the config parameter "log_line_info" and implement the following escapes: %U = user %D = database %T = timestamp %P = pid %L = session log line

Re: [HACKERS] log_line_info plan

2004-02-17 Thread Bruce Momjian
Joshua D. Drake wrote: > Andrew Dunstan wrote: > > > > I am about to redo the patch that would allow tagging of log lines with > > info via a printf-style string. > > > > Current plans are to call the config parameter "log_line_info" and > > implement the following escapes: > > > > %U = user >

Re: [HACKERS] log_line_info plan

2004-02-17 Thread Andrew Dunstan
Joshua D. Drake wrote: Andrew Dunstan wrote: I am about to redo the patch that would allow tagging of log lines with info via a printf-style string. Current plans are to call the config parameter "log_line_info" and implement the following escapes: %U = user %D = database %T = timestamp %P

Re: [HACKERS] log_line_info plan

2004-02-17 Thread Tom Lane
Andrew Dunstan <[EMAIL PROTECTED]> writes: > I am about to redo the patch that would allow tagging of log lines with > info via a printf-style string. > Any comments or suggestions before I start? I think Bruce already applied the previous version of your patch. No problem with yanking it out f

Re: [HACKERS] [GENERAL] Check for prepared statement

2004-02-17 Thread Greg Sabino Mullane
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Fabrizio Mazzoni asked: > How can i find out if a prepared statement already exists..? Is there a > function or a query i can execute ..?? I have not seen an answer to this, and I am curious as well. Anyone? (Cross-posting to hackers due to