Mike Mascari <[EMAIL PROTECTED]> writes:
> ... Would it be possible to have either a GUC setting or a grammar
> change to allow TEMPORARY tables to be dropped at transaction commit?
This seems like a not unreasonable idea; but the lack of other responses
suggests that the market for such a featur
Josh Berkus wrote:
>
> Tom,
>
> > Probably we should have temp table creation allowed to all by default.
> > I'm not convinced that that's a good idea for schema-creation privilege
> > though. Related issues: what should initdb set as the permissions for
> > template1? Would it make sense for
> I think that when SERIAL is used, the sequence should be tied
> inextricably to the table which created it, and it should be hidden from
> use for other purposes (perhaps similar to the way a toast table is). If
> you *want* to use a sequence across several tables, then you don't use
> SERIA
Tom Lane wrote:
> "Rod Taylor" <[EMAIL PROTECTED]> writes:
>
>>>What happens is the sequence is shared between several tables (eg.
>>>invoice numbers or something)
>>
>
>>You cannot accomplish this situation by strictly using the SERIAL
>>type.
>
>
> But Chris is correct that there are borderl
Larry Rosenman wrote:
> > Sorry about the block. RBL+ has been much more effective lately, and it
> > is because they are blocking more dialup users. This the first false
> > positive I have gotten from them. You can use [EMAIL PROTECTED] or
> > route your email through west.navpoint.com. I wi
Larry Rosenman wrote:
> > Sorry about the block. RBL+ has been much more effective lately, and it
> > is because they are blocking more dialup users. This the first false
> > positive I have gotten from them. You can use [EMAIL PROTECTED] or
> > route your email through west.navpoint.com. I wi
> Great!Thanks for your help.
You are welcome.
> Would you please update the Makefile under Unicode?it should be updated
> for GB18030.
done.
--
Tatsuo Ishii
---(end of broadcast)---
TIP 3: if posting/reading through Usenet, please send an appr
David Ford <[EMAIL PROTECTED]> writes:
> I'm using md5 in pg_hba.conf. That is the method, no?
> I'm writing a milter application which instantiates a private resource
> for each thread upon thread startup. I have priv->conn which I
> establish as priv->conn=PQconnectdb(connstr), connstr is co
"Rod Taylor" <[EMAIL PROTECTED]> writes:
>> What happens is the sequence is shared between several tables (eg.
>> invoice numbers or something)
> You cannot accomplish this situation by strictly using the SERIAL
> type.
But Chris is correct that there are borderline cases where we might
do the w
* Bruce Momjian <[EMAIL PROTECTED]> [020613 21:49]:
> Bear Giles wrote:
> > > Sorry, there is a newer version. I will use that one.
> >
> > You may want to hold off on that - I've been busy lately and haven't had
> > a chance to revisit the documentation or change some of the literal constants
>
David Ford wrote:
> I'm using md5 in pg_hba.conf. That is the method, no?
>
> I'm writing a milter application which instantiates a private resource
> for each thread upon thread startup. I have priv->conn which I
> establish as priv->conn=PQconnectdb(connstr), connstr is const char
> *conns
David Ford <[EMAIL PROTECTED]> writes:
> Tom, if you block everyone on cable, dialup, dsl, and adsl, then you're probably
>blocking a lot of legitimate mail.
David, let me explain this in words of one syllable: I am currently
rejecting upwards of 2000 spam messages per day. If I did not have
ex
Bear Giles wrote:
> > Sorry, there is a newer version. I will use that one.
>
> You may want to hold off on that - I've been busy lately and haven't had
> a chance to revisit the documentation or change some of the literal constants
> to numeric constants, but it's been on my "to do" list.
OK,
> What happens is the sequence is shared between several tables (eg.
invoice
> numbers or something)
You cannot accomplish this situation by strictly using the SERIAL
type.
---(end of broadcast)---
TIP 5: Have you checked our extensive FAQ?
http:
> Currently serial is dumped as a sequence and appropriate default
> statement.
>
> With my upcoming dependency patch serials depend on the appropriate
> column. Drop the column (or table) and the sequence goes with it.
> The depencency information does not survive the pg_dump / restore
> process
> Sorry, there is a newer version. I will use that one.
You may want to hold off on that - I've been busy lately and haven't had
a chance to revisit the documentation or change some of the literal constants
to numeric constants, but it's been on my "to do" list.
The latter didn't affect the oth
Your patch has been added to the PostgreSQL unapplied patches list at:
http://candle.pha.pa.us/cgi-bin/pgpatches
I will try to apply it within the next 48 hours.
---
Bear Giles wrote:
> Attached is the first cut
Sorry, there is a newer version. I will use that one.
---
Bear Giles wrote:
> Attached is the first cut at some SSL documetation for the
> PostgreSQL manual. It's in plain text, not DocBook, to make
> editing easy for the
... while talking to sss.pgh.pa.us.:
>> MAIL From:<[EMAIL PROTECTED]>
>>>
>>>
<<< 550 5.7.1 Probable spam from 68.9.71.221 refused - see
http://www.five-ten-sg.com/blackhole.php?68.9.71.221
554 5.0.0 Service unavailable
Tom, if you block everyone on cable, dialup, dsl, and adsl, then
I'm using md5 in pg_hba.conf. That is the method, no?
I'm writing a milter application which instantiates a private resource
for each thread upon thread startup. I have priv->conn which I
establish as priv->conn=PQconnectdb(connstr), connstr is const char
*connstr="host=10.0.0.5 dbname=bmilt
Folks,
> No. IMHO, if we change the naming convention for serial sequences (which
> seems unlikely, except that it might be indirectly affected by changing
> NAMEDATALEN), then we'd *want* the new naming convention to take effect,
> not to have pg_dump scripts force an old naming convention to
Thats fair, and makes the job a heck of a lot simpler.
We do need to change the sequence naming once. They have a tendency
to conflict at the moment.
--
Rod
- Original Message -
From: "Tom Lane" <[EMAIL PROTECTED]>
To: "Rod Taylor" <[EMAIL PROTECTED]>
Cc: "Hackers List" <[EMAIL PROTECTE
"Rod Taylor" <[EMAIL PROTECTED]> writes:
> If we have sequences pick new names automatically, it may not pick the
> same name after dump / restore as it had earlier -- especially across
> versions (see TODO entry).
> So don't we need a way to suggest the *right* name to SERIAL?
No. IMHO, if we c
If we have sequences pick new names automatically, it may not pick the
same name after dump / restore as it had earlier -- especially across
versions (see TODO entry).
So don't we need a way to suggest the *right* name to SERIAL?
--
Rod
- Original Message -
From: "Tom Lane" <[EMAIL PROTE
--
Rod
- Original Message -
From: "Tom Lane" <[EMAIL PROTECTED]>
To: "Rod Taylor" <[EMAIL PROTECTED]>
Cc: "Hackers List" <[EMAIL PROTECTED]>
Sent: Thursday, June 13, 2002 9:46 AM
Subject: Re: [HACKERS] Making serial survive pg_dump
> "Rod Taylor" <[EMAIL PROTECTED]> writes:
> > Store se
Normally I'd agree, but I've found a few people who use normal
sequence operations with serial sequences. That is, they track down
the name and use it.
I'd prefer to force these people to make it manually, but would be
surprised if that was a concensus.
--
Rod
- Original Message -
From:
"Rod Taylor" <[EMAIL PROTECTED]> writes:
> Normally I'd agree, but I've found a few people who use normal
> sequence operations with serial sequences. That is, they track down
> the name and use it.
Sure. But what's this have to do with what pg_dump should emit?
regards
"Rod Taylor" <[EMAIL PROTECTED]> writes:
> Ok, keeping the setval is appropriate. Are there any problems with a
> SERIAL() implementation?
What for? The sequence name is an implementation detail, not something
we want to expose (much less let users modify).
regards, tom
I know you guys love subject lines like this, but I have a humble
request. Would it be possible to have either a GUC setting or a grammar
change to allow TEMPORARY tables to be dropped at transaction commit? I
know the standard defines the lifetimes of temporary tables to be that
of the session. H
> -Original Message-
> From: Michael Meskes [mailto:[EMAIL PROTECTED]]
> Sent: Thursday, June 13, 2002 3:06 AM
> To: [EMAIL PROTECTED]
> Subject: Re: [HACKERS] PostGres Doubt
>
>
> On Wed, Jun 12, 2002 at 11:46:47AM -0700, Dann Corbit wrote:
> > I should apologize for being rather harsh
I have added the recent threads discussing a Win32 port to CVS
TODO.detail, and have added an item on the TODO list:
* Create native Win32 port [win32]
--
Bruce Momjian| http://candle.pha.pa.us
[EMAIL PROTECTED] | (610) 853-3000
+ If your l
got it ... will try and incorporate it and see what I can come up with ...
thanks :)
On Thu, 13 Jun 2002, Bruce Momjian wrote:
> Jeroen T. Vermeulen wrote:
> > On Thu, Jun 13, 2002 at 09:15:05AM -0300, Marc G. Fournier wrote:
> > >
> > > Jeroen ... can you send me a copy of the CVSROOT for thi
Jeroen T. Vermeulen wrote:
> On Thu, Jun 13, 2002 at 09:15:05AM -0300, Marc G. Fournier wrote:
> >
> > Jeroen ... can you send me a copy of the CVSROOT for this? Email will
> > work ... if we can, I would like to save the development history, and I
> > *think* I can ...
>
> I already sent one t
On Thu, Jun 13, 2002 at 09:15:05AM -0300, Marc G. Fournier wrote:
>
> Jeroen ... can you send me a copy of the CVSROOT for this? Email will
> work ... if we can, I would like to save the development history, and I
> *think* I can ...
I already sent one to Bruce last night, IIRC.
Jeroen
> Also, you neglected to add PLACING to the gram.y keyword category lists.
I just now added and committed it as a reserved word.
- Thomas
---(end of broadcast)---
TIP 5: Have you checked our extensive FAQ?
http://www.postgresq
"Rod Taylor" <[EMAIL PROTECTED]> writes:
> Store sequence information in the SERIAL creation statement:
> CREATE TABLE tab (col1 SERIAL(, ));
This is wrong because it loses the separation between schema and data.
I do agree that it would be nice if pg_dump recognized serial columns
and dumped the
Thanks for the info! I have a question...
> As usual: ( ) + * [ ] |
> Instead of dot . there is underscore _
> There is % to mean .* just like LIKE
> There is no ? or ^ or $
> Regular expressions match the whole string, as if there were an
> implicit ^ before and $ after the pattern. You ha
Hi Ishii-san,
Great!Thanks for your help.
Would you please update the Makefile under Unicode?it should be updated
for GB18030.
Best regards,
Bill
Tatsuo Ishii wrote:
>[pgsql-announce removed and pgsql-hackers added]
>
>I have applied your patches with small corrections. Please grab the
>lat
On Thu, 13 Jun 2002, Jeroen T. Vermeulen wrote:
> On Wed, Jun 12, 2002 at 10:41:32PM -0400, Tom Lane wrote:
> >
> > I'm thinking we should just import the current state of the files
> > and not worry about preserving their change history.
>
> Fine with me, if that's easier. I just thought it mig
Currently serial is dumped as a sequence and appropriate default
statement.
With my upcoming dependency patch serials depend on the appropriate
column. Drop the column (or table) and the sequence goes with it.
The depencency information does not survive the pg_dump / restore
process however as i
On Wed, Jun 12, 2002 at 10:41:32PM -0400, Tom Lane wrote:
>
> I'm thinking we should just import the current state of the files
> and not worry about preserving their change history.
Fine with me, if that's easier. I just thought it might be "nice to have"
but I can't think of any compelling re
On Wed, Jun 12, 2002 at 06:19:57PM -0400, Bruce Momjian wrote:
> > I doubt if many people are using it then. There is a NIST SQL suite
> > which should be run against it. Have you heard of it? It is a
> > standardization for embedded SQL [and other facets of the SQL langauge].
> > I think it wo
On Wed, Jun 12, 2002 at 05:42:24PM -0400, Bruce Momjian wrote:
> You are actually the first person to complain about this, as far as I
> can remember.
Yup. I cannot remember any other person either. And since nobody
complained, nobody worked on this. :-)
Michael
--
Michael Meskes
[EMAIL PROTECT
On Wed, Jun 12, 2002 at 11:46:47AM -0700, Dann Corbit wrote:
> I should apologize for being rather harsh about embedded SQL for
> PostgreSQL.
Also about being harsh about the people? Okay, apologies accepted.
> I actually spent a great deal of effort trying to write some tools using
> the Postgr
On Wed, Jun 12, 2002 at 11:00:26AM -0700, Dann Corbit wrote:
> Or run concurrent queries queries at the same time? Or later discover
> the need to do so?
I didn't say multi-threading is bad. I just don't think your answer
helped him much.
> I posted the problems to this list long ago. I wanted
Christopher Kings-Lynne wrote:
>
> > > Hrm - last time I checked it did...
> >
> > Two questions :
> >
> > When was the last time ?
>
> 7.1
>
> > It did what ?
>
> Drops triggers and stuff.
>
> OK, I did a check and it looks like it's fixed in 7.2 at least. Sorry for
> the false alarm...
It
> > Hrm - last time I checked it did...
>
> Two questions :
>
> When was the last time ?
7.1
> It did what ?
Drops triggers and stuff.
OK, I did a check and it looks like it's fixed in 7.2 at least. Sorry for
the false alarm...
Chris
---(end of broadcast)---
On Thu, 2002-06-13 at 03:47, Christopher Kings-Lynne wrote:
> > > What is a TRUNCATE TABLE but a drop create anyway? Is there some
> > > technical difference?
> > >
> > It doesn't kill indexes/triggers/constraints/Foreign Key Stuff, etc.
>
> Hrm - last time I checked it did...
Two questions :
On Wed, 2002-06-12 at 19:38, Tom Lane wrote:
> David Ford <[EMAIL PROTECTED]> writes:
> > So reentrancy in libpq basically is put on hold until 7.3.
>
> Only if you insist on using "crypt", which is deprecated anyway.
> md5 is the preferred encryption method.
>
> My feeling about the proposed pa
[pgsql-announce removed and pgsql-hackers added]
I have applied your patches with small corrections. Please grab the
latest source and let me know if something is wrong.
Thanks.
--
Tatsuo Ishii
> Hi Ishii-san,
>
> The patches are attached.Please apply it.
>
> Thanks,
> Bill
>
> Tatsuo Ishii
50 matches
Mail list logo
