Folks,
Thanks, all! Now, if only I could remember who asked me the question ...
--
Josh Berkus
Aglio Database Solutions
San Francisco
---(end of broadcast)---
TIP 1: if posting/reading through Usenet, please send an appropriate
subscribe-n
Tom,
> > That sounds good if it works. However ... will an add_missing_from view
> > work if add_missing_from is off in the session where the query is
> > executed?
>
> Yes, you only need to get it past the parser during CREATE VIEW.
Then the proposal sounds like a good solution to me. It woul
Thanks! Any reason the comment shouldn't also mention this directly? I.E.:
/*
This covers the long options equivalent to -X xxx.
The -X options return 0 if called in long form, because then we store a flag
rather than returning a distinct value.
See man 3 getopt.
*/
Sean
- Original Message
Josh Berkus writes:
> That sounds good if it works. However ... will an add_missing_from view work
> if add_missing_from is off in the session where the query is executed?
Yes, you only need to get it past the parser during CREATE VIEW.
regards, tom lane
---
OK, I think I see it. The problem is that the code in slru.c is careful
about not modifying state when it doesn't hold the proper lock, but not
so careful about not *inspecting* state without the proper lock. In
particular consider these lines in SimpleLruReadPage (line numbers are
as in CVS tip)
You have omitted the "case 0" line following the comment, which is in
fact what it refers to. The -X options return 0 if called in long form,
because then we store a flag rather than returning a distinct value. See
man 3 getopt.
cheers
andrew
Sean Utt wrote:
In what might be called my spa
In what might be called my spare time, I was looking at pg_dump.c to see
about adding an option to dump only functions, and I think a comment got
pushed out of place in the section for handling arguments:
395 case 'X':
396 if (strcmp
> >> http://developer.postgresql.org/~devrim/rpms/8.1/rc1
> >
> > The developer.postgresql.org machine really isn't geared to handle
> > downloads.. Any reason you can't just stick it on the standard ftp
> > sites and have it mirrored along with everything else?
>
> This is taken from our spec:
Hi,
On Sun, 30 Oct 2005, Magnus Hagander wrote:
http://developer.postgresql.org/~devrim/rpms/8.1/rc1
The developer.postgresql.org machine really isn't geared to handle
downloads.. Any reason you can't just stick it on the standard ftp sites
and have it mirrored along with everything else?
> > Take a look through it, will announce this evening ...
>
> Could you please include RPMs in your announcement? They
> *will* be here:
>
> http://developer.postgresql.org/~devrim/rpms/8.1/rc1
The developer.postgresql.org machine really isn't geared to handle
downloads.. Any reason you can't
Andrew,
> My suggestion was to set add_missing_from _in the output of pg_dump_ (or
> pg_restore) so that affected views would restore correctly. This would
> affect only the session in which the dump was restored. The changes that
> were already suggested (and since implemented, iiuc) would then m
Marc,
I just finished a build with the 8.1beta4 for Solaris 8 (SPARC) with:
OpenSSL 0.9.8
Heimdal 0.7
tcl/tk-8.4.8
perl-5.8.4
using gcc-3.4.3 and the following compile command:
gcc -O3 -DOPENSSL_DISABLE_OLD_DES_SUPPORT -fno-sched-interblock
All tests passed successfully.
Ken
On Mon, Oct 24
Andrew Dunstan wrote:
Kevin Murphy wrote:
Would you try the attached patch and see if it
gets rid of the warnings? Also check that regression tests and contrib
build/regression tests still work.
Tom, That patch worked, as far as eliminating those duplicate symbol
warnings. I have some dep
On 10/26/05, Christopher Kings-Lynne <[EMAIL PROTECTED]> wrote:
> > iconv -c -f UTF8 -t UTF8
> recode UTF-8..UTF-8 < dump_in.sql > dump_out.sql
I've got a file with characters that pg won't accept that recode does
not fix but iconv does. Iconv is fine for my application, so I'm just
posting to t
On 2005-10-30, Robert Treat <[EMAIL PROTECTED]> wrote:
> Actually I rather liked your solution, except that it probably doesn't do
> enough to get people off that setting as others want. Ie. I generally run
> with that setting on, but I certainly don't make views/rules/etc.. that rely
> on that
On Wednesday 26 October 2005 15:33, Andrew - Supernews wrote:
> On 2005-10-26, Tom Lane <[EMAIL PROTECTED]> wrote:
> > Andrew - Supernews <[EMAIL PROTECTED]> writes:
> >> On 2005-10-26, Tom Lane <[EMAIL PROTECTED]> wrote:
> >>> Pretending it's the user's mistake isn't
> >>> an answer that fits down
Hi,
Martijn van Oosterhout writes:
You solve it by allowing other backends to lock and examine your
temporary tables. But AIUI temporary tables are not stored in shared
memory so how do you get a consistant view of it?
Not unsolvable, but very tricky.
Right, the problem isn't that "it can
17 matches
Mail list logo
