Registration is easy, and pretty much anonymous... worth to promote our
beloved database. :)
Happy New Year,
Daniel
Marc G. Fournier said:
Just got this in my mailbox:
2002 LinuxQuestions.org Members Choice Awards:
On Thu, 2 Jan 2003 01:44:21 -0500, Serguei Mokhov [EMAIL PROTECTED] wrote:
Either way, something has to be donw about this...
Just another way to do it:
#if defined(HAVE_GETOPT_LONG)
#define PARMPREFIX '='
#else
#define PARMPREFIX ' '
#endif
static void
explain_option(char *shortform, char
Hi all,
I have come across some weird behavior in postgres concerning autocommit=off
and setting the transaction isolation level. I have no explanation why
things should work as they do, so I consider this a bug, no?
With autocommit=on and normal begin; ... commit; block setting the
transaction
I'll do that. Justin: What's the URL for the .pgpass stuff? So far I see
mention of using SSL. That's two items to cover. Anything else?
On Wed, 1 Jan 2003, Bruce Momjian wrote:
Yes, I have been feeling we should do that. Justin pointed out just
yesterday that .pgpass is only mentioned
Manfred Koizar [EMAIL PROTECTED] writes:
Just another way to do it:
#define xo explain_option
xo(f, file, FILENAME, output file name);
Perhaps better would be:
#if defined(HAVE_GETOPT_LONG)
#define xo(long,short,desc) printf(%-27s %s\n, long, desc)
#else
#define xo(long,short,desc)
Michael Paesold [EMAIL PROTECTED] writes:
Now setting autocommit=off the set transaction isolation level command does
not show any effect:
billing=# set autocommit to off;
SET
billing=# set transaction isolation level serializable;
SET
SET does not start a transaction block, so this will
On Thu, 2 Jan 2003, Tom Lane wrote:
Michael Paesold [EMAIL PROTECTED] writes:
Now setting autocommit=off the set transaction isolation level command does
not show any effect:
billing=# set autocommit to off;
SET
billing=# set transaction isolation level serializable;
SET
SET does
Dan Langille wrote:
I'll do that. Justin: What's the URL for the .pgpass stuff? So far I see
mention of using SSL. That's two items to cover. Anything else?
Hi Dan,
Very Cool. The URL for the .pgpass stuff is:
http://developer.postgresql.org/docs/postgres/libpq-files.html
:-)
Regards
On Fri, 3 Jan 2003, Justin Clift wrote:
Very Cool. The URL for the .pgpass stuff is:
http://developer.postgresql.org/docs/postgres/libpq-files.html
There is a typo on that page. First it talkes about the file .pgpass and
then it says: chmod 0600 .pgaccess.
I had no idea that one could
- Original Message -
From: Tom Lane [EMAIL PROTECTED]
Sent: January 02, 2003 9:29 AM
Maybe we should not try to be cute, but just do
#if defined(HAVE_GETOPT_LONG)
#define xo(long,short,desc) printf(%s %s\n, long, desc)
#else
#define xo(long,short,desc) printf(%s %s\n, short,
Postgresql is first, now (51%, mysql 35%)
regards
Haris Peco
On Thursday 02 January 2003 08:53, Daniel Kalchev wrote:
Registration is easy, and pretty much anonymous... worth to promote our
beloved database. :)
Happy New Year,
Daniel
Marc G. Fournier said:
Just got this in my
I think I initially forgot those options, and Stephans patch seems to be
everything required -- though the psql display is a little more
cluttered.
pg_get_constraintdef should probably be looking at condeferrable
and condeferred in the pg_constraint row it's looking at. Maybe something
like
Serguei Mokhov [EMAIL PROTECTED] writes:
Looks good to me, but there is still a little inconvenience
of multiline option descriptions, and the above won't handle
it nicely.
True, a multiline description would have to look like
xo(_(-f, --file=FILENAME),
_(-f FILENAME
On 2 Jan 2003, Rod Taylor wrote:
I think I initially forgot those options, and Stephans patch seems to be
everything required -- though the psql display is a little more
cluttered.
IIRC, theoretically only initially immediate deferrable actually
needs to specify both clauses (initially
Rod Taylor [EMAIL PROTECTED] writes:
I think I initially forgot those options, and Stephans patch seems to be
everything required -- though the psql display is a little more
cluttered.
Yeah, it is. Could we improve that by having pg_get_constraintdef add
text only when the setting isn't the
Shahbaz == Shahbaz Chaudhary [EMAIL PROTECTED] writes:
Shahbaz There are bound to be people in the academia (grad
Shahbaz students, professors of CS, etc.) on this mailing list,
Shahbaz yet I see few RDBMS courses using postgresql as an
Shahbaz example. If people still have
Hi!
subject says it all, I guess. There is hardly no difference between 7.3
libpq and 7.3.1 libpq. Why the version shift? Isn't the only thing
rectifying a version shift that there is a change in the API. Maybe there
is, but I cannot find it.
If there is a good reason, like say security,
It's that time of year again, when I remind everyone just how difficult life
in the trenches with PostgreSQL can be, when the life in the trenches
involves upgrades. If you don't want to read about it, then please hit
DELETE in you e-mail (or nntp) client.
I'll not get too vehement this time
On Thu, 2 Jan 2003, Marc G. Fournier wrote:
Just got this in my mailbox:
2002 LinuxQuestions.org Members Choice Awards:
http://www.linuxquestions.org/questions/showthread.php?s=78a8c06fbc1dcecd52597decd6c56ad8threadid=39870
And we are way behind MySQL (like, d'ah!):
Yeah, the registration was painless and enough options to disable it
annoying you. Count my vote cast for PostgreSQL. I encourage everyone
else to do the same. In the big picture, marketing statements like this
survey mean alot more than most technical folks want to acknowledge.
Please
- Original Message -
From: Tom Lane [EMAIL PROTECTED]
Sent: January 02, 2003 1:58 PM
Serguei Mokhov [EMAIL PROTECTED] writes:
Looks good to me, but there is still a little inconvenience
of multiline option descriptions, and the above won't handle
it nicely.
True, a multiline
See http://polls.unixathome.org/
Goal: create a voting script which uses PostgreSQL to store the data.
--
Dan Langille : http://www.langille.org/
---(end of broadcast)---
TIP 4: Don't 'kill -9' the postmaster
On 2 Jan 2003 at 7:53, Charles H. Woloszynski wrote:
Yeah, the registration was painless and enough options to disable it
annoying you. Count my vote cast for PostgreSQL. I encourage everyone
else to do the same. In the big picture, marketing statements like
this survey mean alot more than
Serguei Mokhov [EMAIL PROTECTED] writes:
Now, this:
#if defined(HAVE_GETOPT_LONG)
#define xo(long,short,desc) printf(%s %s\n, long, desc)
#else
#define xo(long,short,desc) printf(%s %s\n, short, desc)
#endif
seems relatively generic, so it could be used by more than one tool.
But
On Thu, Jan 02, 2003 at 03:07:48PM -0500, Dan Langille wrote:
else to do the same. In the big picture, marketing statements like
this survey mean alot more than most technical folks want to
acknowledge.
The figures would be a lot more interesting anyway if people bothered
to correlate
On 2 Jan 2003 at 21:30, Jeroen T. Vermeulen wrote:
Coincidentally, I've just started up a voting script project... see
http://polls.unixathome.org/
Does it support hanging chads?
Now is the time to decide that
--
Dan Langille : http://www.langille.org/
Your patch has been added to the PostgreSQL unapplied patches list at:
http://momjian.postgresql.org/cgi-bin/pgpatches
I will try to apply it within the next 48 hours. It also will be
backpatched.
---
Stephan
On Thu, Jan 02, 2003 at 07:26:06PM -0500, Tom Lane wrote:
Lamar Owen [EMAIL PROTECTED] writes:
replies I will rather quickly redirect to /dev/null, as it isn't Red Hat's
fault we can't do a sane upgrade.
I think you're wasting your time trying to hold us to a higher standard
of
(moved from PATCHES back to HACKERS)
Tom Lane wrote:
Oh, you're thinking about the multi-column aspect of it, not the
multi-row aspect. You really ought to keep those strictly separate;
their design and implementation problems are quite different IMHO.
I find it quite confusing to refer to
- Original Message -
From: Tom Lane [EMAIL PROTECTED]
Sent: January 02, 2003 3:20 PM
#if defined(HAVE_GETOPT_LONG)
#define xo(long,short,desc) printf(%s %s\n, long, desc)
#else
#define xo(long,short,desc) printf(%s %s\n, short, desc)
#endif
seems relatively generic, so it
Bruce Momjian writes:
Yes, I have been feeling we should do that. Justin pointed out just
yesterday that .pgpass is only mentioned in libpq documentation, and in
fact there is lots of stuff mentioned in libpq that releates to the
other interfaces, so it should be pulled out and put in one
Serguei Mokhov [EMAIL PROTECTED] writes:
But there's no good place to put it. I'd say just stick it into each
tool; it's no worse than repeating the existence of a usage()
subroutine in each tool.
It ended up being in dumputils.h
I really don't like putting a macro with a name as short as
Peter Eisentraut [EMAIL PROTECTED] writes:
Bruce Momjian writes:
Yes, I have been feeling we should do that. Justin pointed out just
yesterday that .pgpass is only mentioned in libpq documentation, and in
fact there is lots of stuff mentioned in libpq that releates to the
other interfaces,
Dennis Björklund wrote:
On Fri, 3 Jan 2003, Justin Clift wrote:
Very Cool. The URL for the .pgpass stuff is:
http://developer.postgresql.org/docs/postgres/libpq-files.html
There is a typo on that page. First it talkes about the file .pgpass and
then it says: chmod 0600 .pgaccess.
Tom Lane wrote:
Peter Eisentraut [EMAIL PROTECTED] writes:
Bruce Momjian writes:
Yes, I have been feeling we should do that. Justin pointed out just
yesterday that .pgpass is only mentioned in libpq documentation, and in
fact there is lots of stuff mentioned in libpq that releates to the
Bruce Momjian [EMAIL PROTECTED] writes:
Also, does anyone know why the development docs are 7.3.1?
Because it was pointed to that branch during the 7.3 beta cycle.
It needs to be repointed to CVS tip. I dunno how to do so, however.
Is someone working to get 7.3.1 announced on our main web
Lamar Owen [EMAIL PROTECTED] writes:
So I figured I'd roll a 7.1.3 RPMset for him to install onto Red Hat 8. It
was very bad. It simply would not build -- I guess it's the gcc 3
stuff.
If you don't know *exactly* why it doesn't build, I don't think you
should be blaming us for it. (FWIW, I
37 matches
Mail list logo
