I hope you mean 'redundant with "PRIMARY KEY" in example'...
Works out the same way though.
Chris
Neil Conway wrote:
Log Message:
---
Minor doc tweak: "NOT NULL" is redundant with "SERIAL" in example.
Modified Files:
--
pgsql/doc/src/sgml/ref:
create_domain.sgm
Hello,
it depend on your possibilities. Simply, use PL/Perl or PL/sh.
Regards
Pavel Stehule
or use PgSendMail
http://sourceforge.net/project/showfiles.php?group_id=35804
Hi there,
How can i send mail form postgresql.
any suggestion.
thanx & regards
aftab
---(end of
Simon Riggs wrote:
> The TODO list has an item "add missing date selectivity", which is a
> hang-over from 1999 or before.
>
> Is this still an issue? Can somebody describe exactly what it is?
>
> I can't find the exact discussion of what the problem was/is, so its
> better to ask directly...
Go
Hi there,
How can i send mail form postgresql.
any suggestion.
thanx & regards
aftab
---(end of broadcast)---
TIP 6: explain analyze is your friend
Hannu Krosing <[EMAIL PROTECTED]> writes:
> making one of WAL files (strategies) be /dev/null would almost get us
> non-logged writes, except for a little overhead in write() calls.
> fsync() on /dev/null should be instantaneous .
No, you really do want to push it up to a higher level than that.
T
I wrote:
You probably need to fix the max-connections pass so that it applies the
same changes to max_fsm_pages as the second pass does --- otherwise, its
assumption that shared_buffers can really be set that way will be wrong.
Other than that I didn't see any problem with the shared_buffers
"Andrew Dunstan" <[EMAIL PROTECTED]> writes:
> Greg Stark said:
> > Well fwiw what pg_dump does isn't even considered a "backup" at all in
> > other systems. It's a "logical export" or something of that sort.
> >
> > It's not considered a "backup" because it's saving something different
> > than
Ühel kenal päeval, R, 2005-12-23 kell 23:06, kirjutas Tom Lane:
> Greg Stark <[EMAIL PROTECTED]> writes:
> > It seems to me the only rational way to approach this is to have a per-table
> > flag that sets that table to be non-logged. Essentially changing a table's
> > behaviour to that of a tempora
Ühel kenal päeval, T, 2005-12-27 kell 19:20, kirjutas Martijn van
Oosterhout:
> On Mon, Dec 26, 2005 at 11:00:51AM -0500, Bruce Momjian wrote:
> >
> > I think this brings up an interesting distinction, that having the NO
> > LOGGING switch per command doesn't make sense because it modifying the
>
I wrote:
> Michael Paesold <[EMAIL PROTECTED]> writes:
>> I am seeing a similar unique index bug here...
>> This is PostgreSQL 8.1.1 on RHEL 3, Intel Xeon (i686).
> It looks like the problem is that index entries are being inserted out
> of order.
After further investigation, it seems that the or
Of course having the ability to execute arbitrary plpgsql in .sql
scripts would be handy in some cases as well, though as others pointed
out there are alternatives.
I don't know if it's possible. PL/pgSQL parser live in different context
than SQL parser and PostgreSQL supports more languages th
Michael Paesold <[EMAIL PROTECTED]> writes:
> I am seeing a similar unique index bug here...
> This is PostgreSQL 8.1.1 on RHEL 3, Intel Xeon (i686).
It looks like the problem is that index entries are being inserted out
of order. I find this pair that should be in the other order:
Item 124 --
Greg Stark said:
> Bruce Momjian writes:
>
>> I noticed that we are using the term "Online Backup" in our
>> documentation when we are talking about continuous backup and PITR.
>>
>> To me, "online backup" is doing a backup while the system is online
>> (online-backup), and that is accomplished by
Bruce Momjian writes:
>> This addresses the technical workings of the various backup systems.
>> The fact that it is or isn't on-line, hot, continuous, fast, or flexible
>> is secondary.
> To me, the continuous activity is the significant feature of that backup
> method. I chose "Continuous Back
Bruce Momjian writes:
> I noticed that we are using the term "Online Backup" in our
> documentation when we are talking about continuous backup and PITR.
>
> To me, "online backup" is doing a backup while the system is online
> (online-backup), and that is accomplished by pg_dump.
Well fwiw w
On Mon, Dec 26, 2005 at 11:00:51AM -0500, Bruce Momjian wrote:
>
> I think this brings up an interesting distinction, that having the NO
> LOGGING switch per command doesn't make sense because it modifying the
> table. It has to be a per-object switch, or something that operates
> only on empty t
Peter Eisentraut wrote:
> I've noticed some inconsistencies in the handling of build-time enabled GUC
> setttings. For example, a non-SSL enabled server will happily accept ssl =
> on and simply ignore it. On the other hand, several syslog related
> parameters are not accepted at all when sysl
Peter Eisentraut wrote:
> Am Montag, 26. Dezember 2005 20:46 schrieb Heikki Linnakangas:
> > FWIW, I believe "log archival" is a common term for that.
>
> I like that better, although there are a lot of logs, so maybe
> "transaction log archival".
Yep, when I think of log archiving, I think of sa
On Thu, Dec 22, 2005 at 06:35:24PM -0500, Bruce Momjian wrote:
> Hannu Krosing wrote:
> > ?hel kenal p?eval, N, 2005-12-22 kell 18:19, kirjutas Bruce Momjian:
> > I guess he rather wants to have dont-save-but-execute-immediately
> > pl/pgsql code.
> >
> > could this perhaps be solved by having tem
On Sat, Dec 24, 2005 at 02:01:17AM -0500, Greg Stark wrote:
> But I like the other user's suggestion too. If there's a standards blessed
> feature to have temporary tables that are visible in other sessions then
> perhaps that's what we've arrived at from another direction.
Having a temporary tabl
Rod Taylor schrieb:
On Wed, 2005-11-09 at 14:20 -0500, Tom Lane wrote:
Rod Taylor <[EMAIL PROTECTED]> writes:
As you can see, we have duplicates within the table (heap) of a primary
key value. The index itself only references one of these tuples.
Can you put together a test case to reproduce t
Greetings all,
If you're not interested in COLLATE, operator classes or related
things, stop now, this is quite a long email.
Firstly, status. PostgreSQL doesn't really support collations at all.
The order of strings is defined at initdb time by the locale then and
cannot be changed later. We all
Am Montag, 26. Dezember 2005 20:46 schrieb Heikki Linnakangas:
> FWIW, I believe "log archival" is a common term for that.
I like that better, although there are a lot of logs, so maybe "transaction
log archival".
Considering the list originally referenced:
- File system backup
- SQL dump
- (Tr
I've noticed some inconsistencies in the handling of build-time enabled GUC
setttings. For example, a non-SSL enabled server will happily accept ssl =
on and simply ignore it. On the other hand, several syslog related
parameters are not accepted at all when syslog is not enabled.
I propose th
24 matches
Mail list logo
