On Sat, 2002-10-12 at 11:37, Gavin Sherry wrote:
> I cannot think of any reason why changing column order should be
> implemented in Postgres. Seems like a waste of time/more code bloat for
> something which is strictly asthetic.
>
> Regardless, I do have collegues/clients who ask when such a fe
Denis A Ustimenko <[EMAIL PROTECTED]> writes:
> On Sun, Oct 13, 2002 at 10:59:40PM -0700, Joe Conway wrote:
>> Well, if we were specifying the timeout in microseconds instead of seconds,
>> it would make sense to have better resolution. But when you can only
>> specify the timeout in seconds, th
Bruce Momjian <[EMAIL PROTECTED]> writes:
> Return last command of INSTEAD rule for tuple count/oid/tag for rules, SPI
> If we are going to fix it, this week is the time. If not, it stays on
> TODO.
If we've agreed on the behavior, I'll try to take care of making it
happen. Note that wil
Joe Conway wrote:
> Bruce Momjian wrote:
> > It could be argued that our seconds are not as exact as they could be
> > with subsecond timing. Not sure it is worth it, but I can see the
> > point.
>
> Well, if we were specifying the timeout in microseconds instead of seconds, it
> would make sen
Alessio Bragadini wrote:
> On Sat, 2002-10-12 at 11:37, Gavin Sherry wrote:
>
> > I cannot think of any reason why changing column order should be
> > implemented in Postgres. Seems like a waste of time/more code bloat for
> > something which is strictly asthetic.
> >
> > Regardless, I do have c
On Mon, Oct 14, 2002 at 11:04:07AM -0400, Bruce Momjian wrote:
> Alessio Bragadini wrote:
> > On Sat, 2002-10-12 at 11:37, Gavin Sherry wrote:
> >
> > > I cannot think of any reason why changing column order should be
> > > implemented in Postgres. Seems like a waste of time/more code bloat for
>
Bruce Momjian <[EMAIL PROTECTED]> writes:
>> Already done -- that's what Denis is unhappy about.
> OK, I see that, but now, we are stuffing everything into a timeval
> struct. Does that make sense? Shouldn't we just use time_t?
Yeah, the code could be simplified now. I'm also still not happy
Tom Lane wrote:
> Bruce Momjian <[EMAIL PROTECTED]> writes:
> >> Already done -- that's what Denis is unhappy about.
>
> > OK, I see that, but now, we are stuffing everything into a timeval
> > struct. Does that make sense? Shouldn't we just use time_t?
>
> Yeah, the code could be simplified n
Hello !
I'd like to translate the advocacy site to Romanian,
as long as nobody else has already offered himself/herself
to do it.
Just tell me, please, what should i do.
Adrian Maier
([EMAIL PROTECTED])
---(end of broadcast)---
TIP 1: subscribe
I'm about to go off and implement this, so just to make sure we are all
on the same page, here's what I think we agreed to:
In the presence of rewrite rules, the command status returned by a
rewritable query will behave thusly:
1. If the original query is executed (ie, there is no unconditional
Hi Adrian,
Wow. That's pretty cool. :)
No-one has offered to do Romanian yet, so you're very welcome to.
First things first:
- What is the two letter language identifier most often used for
Romanian? i.e. fr = Franch, de = German, etc. ro?
- What is the character set that should be used
I just noticed that rewriteHandler.c contains a subroutine orderRules()
that reorders the rules for a relation into the order
non-instead rules
qualified instead rules
unqualified instead rules
This conflicts with the feature we'd added to 7.3 to fire rules in
alphabetical
Bruce Momjian <[EMAIL PROTECTED]> writes:
> That whole remains structure should be a time_t variable, and then we
> _know_ we can't assume it is signed. The use of timeval should
> happen only in pqWaitTimed because it has to use select().
I think it's fine to use struct timeval as the parameter
Yeah I think that could have happened since I was running it several times and had
cancelled it (ctrl-c) it a couple of those times. Could be the backend of one
cancelled run hadn't finished what it was doing and if that was renabling
triggers it could have walked on it.
Thanks.
L.
On Sat, 12
After turning autocommit off on my test database, my cron scripts that
vacuum the database are now failing.
This can be easily reproduced, turn autocommit off in your
postgresql.conf, then launch psql and run a vacuum.
[blind@blind databases]$ psql files
Welcome to psql 7.3b2, the PostgreSQL i
Yep, that's them. This is a big win from a PostgreSQL advocacy position,
especially since oracle pr made an official statement against the use of
PostgreSQL. Has this info hit any of the linux oriented news sites
(linux-today, slashdot, etc...) If not someone from the PostgreSQL
marketing dept. (w
It's on Slashdot, but there's only one post there that mentions the use of
Postgresql.
On 14 Oct 2002, Robert Treat wrote:
> Yep, that's them. This is a big win from a PostgreSQL advocacy position,
> especially since oracle pr made an official statement against the use of
> PostgreSQL. Has this
On Monday 14 October 2002 04:08 pm, Robert Treat wrote:
> Yep, that's them. This is a big win from a PostgreSQL advocacy position,
> especially since oracle pr made an official statement against the use of
> PostgreSQL. Has this info hit any of the linux oriented news sites
> (linux-today, slashdo
Laurette Cisneros <[EMAIL PROTECTED]> writes:
> Yeah I think that could have happened since I was running it several times and had
> cancelled it (ctrl-c) it a couple of those times. Could be the backend of one
> cancelled run hadn't finished what it was doing and if that was renabling
> trigger
Great. I am working my way toward 7.3 anyway...
Thanks!
L.
On Mon, 14 Oct 2002, Tom Lane wrote:
> Laurette Cisneros <[EMAIL PROTECTED]> writes:
> > Yeah I think that could have happened since I was running it several times and had
> > cancelled it (ctrl-c) it a couple of those times. Could be
Hi everyone,
The Turkish translation of the PostgreSQL "Advocacy and Marketing" site,
done by Devrim GUNDUZ <[EMAIL PROTECTED]> is now complete and
ready for public use:
http://advocacy.postgresql.org/?lang=tr
Pretty cool stuff. Thanks Devrim. :-)
Regards and best wishes,
Justin Clift
--
Tom Lane wrote:
> Bruce Momjian <[EMAIL PROTECTED]> writes:
> > That whole remains structure should be a time_t variable, and then we
> > _know_ we can't assume it is signed. The use of timeval should
> > happen only in pqWaitTimed because it has to use select().
>
> I think it's fine to use str
"Michael Paesold" <[EMAIL PROTECTED]> writes:
> In a PL/pgSQL function I want to insert into a table and get the OID back.
> That usually works with
> GET DIAGNOSTICS last_oid = RESULT_OID;
> right after the insert statement.
> But if the table that I insert to has a rule (or perhaps a trigger?)
Oops, overoptimized a little. ptmp_timeout is needed in case no time is
passed; ptmp_timeout restored.
---
pgman wrote:
> Tom Lane wrote:
> > Bruce Momjian <[EMAIL PROTECTED]> writes:
> > > That whole remains structure sho
I have applied the following comment patch. The current code resets the
timer when select() is interruped. On OS's that modify timeout to show
the remaining time, we should be using that value instead of resetting
the timer to its original value on select retry.
---
On Sat, 12 Oct 2002, Tom Lane wrote:
> Steven Singer <[EMAIL PROTECTED]> writes:
> get_namespace_name(RelationGetNamespace(tg_relation))
> Is this sufficiently useful to justify adding an SPI_getrelnamespace()
> function? I'm not very clear on the uses for SPI_getrelname(). Most
> of the
Bruce Momjian <[EMAIL PROTECTED]> writes:
> /*
>* select() may modify timeout argument on some platforms so
> ! *use copy.
> ! *XXX Do we really want to do that? If select() returns
> ! *the number of seconds rem
The Internet Society (ISOC) won the bid to replace Verisign as the .org
registry. They're going to subcontract to Afilias, who has been running the
.info registry.
See:
http://www.icann.org/announcements/announcement-14oct02.htm
http://www.afilias.info/about_afilias/dotorg/index_html
http://www.w
"David De Graff" <[EMAIL PROTECTED]> writes:
> The Internet Society (ISOC) won the bid to replace Verisign as the .org
> registry. They're going to subcontract to Afilias, who has been running the
> .info registry.
Cool.
> See:
> http://www.icann.org/announcements/announcement-14oct02.htm
> http
Tom Lane wrote:
> Bruce Momjian <[EMAIL PROTECTED]> writes:
> > /*
> >* select() may modify timeout argument on some platforms so
> > ! *use copy.
> > ! *XXX Do we really want to do that? If select() returns
> > ! *
Tom, excuse me, I forget to copy previous posting to [EMAIL PROTECTED]
On Mon, Oct 14, 2002 at 09:53:27AM -0400, Tom Lane wrote:
> Denis A Ustimenko <[EMAIL PROTECTED]> writes:
> > On Sun, Oct 13, 2002 at 10:59:40PM -0700, Joe Conway wrote:
> >> Well, if we were specifying the timeout in microsec
> Yep, that's them. This is a big win from a PostgreSQL advocacy position,
> especially since oracle pr made an official statement against the use of
> PostgreSQL. Has this info hit any of the linux oriented news sites
> (linux-today, slashdot, etc...) If not someone from the PostgreSQL
> marketin
Tom Lane wrote:
> I just noticed that rewriteHandler.c contains a subroutine orderRules()
> that reorders the rules for a relation into the order
> non-instead rules
> qualified instead rules
> unqualified instead rules
> This conflicts with the feature we'd added to 7.3 to fire
Barry Lind wrote:
> After turning autocommit off on my test database, my cron scripts that
> vacuum the database are now failing.
>
> This can be easily reproduced, turn autocommit off in your
> postgresql.conf, then launch psql and run a vacuum.
>
> [blind@blind databases]$ psql files
> Welco
Robert Treat wrote:
> Yep, that's them. This is a big win from a PostgreSQL advocacy position,
> especially since oracle pr made an official statement against the use of
> PostgreSQL. Has this info hit any of the linux oriented news sites
> (linux-today, slashdot, etc...) If not someone from the P
At 12:49 AM 14/10/2002 -0400, Bruce Momjian wrote:
> Fix pg_dump to handle 64-bit off_t offsets for custom format
I'll try to get back to this in the next day or so...
Philip Warner| __---_
Alba
Bruce Momjian <[EMAIL PROTECTED]> writes:
> I am sure the problem is that psql doing a query on startup:
Yeah, and libpq does one too in some cases :-(. Both of these need to
be fixed before 7.3 if possible.
Whether we fix these or not, it'd be a good idea to document that
turning autocommit of
Tom Lane wrote:
> Yeah, and libpq does one too in some cases :-(. Both of these need to
> be fixed before 7.3 if possible.
>
> Whether we fix these or not, it'd be a good idea to document that
> turning autocommit off in postgresql.conf is not yet well-supported.
> I doubt that all client-side c
Denis A Ustimenko wrote:
> Tom, excuse me, I forget to copy previous posting to [EMAIL PROTECTED]
>
> On Mon, Oct 14, 2002 at 09:53:27AM -0400, Tom Lane wrote:
> > Denis A Ustimenko <[EMAIL PROTECTED]> writes:
> > > On Sun, Oct 13, 2002 at 10:59:40PM -0700, Joe Conway wrote:
> > >> Well, if we we
Bruce Momjian <[EMAIL PROTECTED]> writes:
> Denis A Ustimenko wrote:
>> Beware of almost 1 second posiible error. For example: connect_timeout == 1,
>> we start at 0.99 then finish_time == 1. If CPU is quite busy we will
>> do only one iteration. I don't know is it enough to make connection?
>
Looking at a 7.2.3 dump of a database I've been using for development, I
noticed that a type that was used in a ALTER TABLE ADD COLUMN (for an
existing table) was CREATE TYPE **AFTER** the CREATE TABLE for said
table.
I suspect this will give me grief on reload.
(I can get around it, but I tho
Tom Lane wrote:
> Bruce Momjian <[EMAIL PROTECTED]> writes:
> > Denis A Ustimenko wrote:
> >> Beware of almost 1 second posiible error. For example: connect_timeout == 1,
> >> we start at 0.99 then finish_time == 1. If CPU is quite busy we will
> >> do only one iteration. I don't know is it en
42 matches
Mail list logo
