forked from MaterializeInc/materialize
-
Notifications
You must be signed in to change notification settings - Fork 0
/
Cargo.toml
77 lines (75 loc) · 2.08 KB
/
Cargo.toml
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
[workspace]
members = [
"demo/billing",
"fuzz",
"play/json-flattened-view-gen",
"play/mbta",
"src/avro",
"src/avro-derive",
"src/aws-util",
"src/build-info",
"src/ccsr",
"src/coord",
"src/coordtest",
"src/dataflow-bin",
"src/dataflow-types",
"src/dataflow",
"src/dataflowd",
"src/expr",
"src/expr-test-util",
"src/http-proxy",
"src/interchange",
"src/kafka-util",
"src/lowertest",
"src/lowertest-derive",
"src/materialized",
"src/metabase",
"src/mzcloud-cli",
"src/mz-process-collector",
"src/ore",
"src/peeker",
"src/persist",
"src/persist-types",
"src/pid-file",
"src/pgrepr",
"src/pgtest",
"src/pgwire",
"src/postgres-util",
"src/prof",
"src/protoc",
"src/repr",
"src/repr-test-util",
"src/sql",
"src/sqllogictest",
"src/sql-parser",
"src/symbiosis",
"src/testdrive",
"src/transform",
"src/walkabout",
"test/chaos",
"test/correctness",
"test/metabase/smoketest",
"test/performance/perf-kinesis",
"test/performance/perf-upsert",
"test/performance/s3-datagen",
"test/test-util",
]
[profile.dev.package]
# Compile the backtrace crate and its dependencies with all optimizations, even
# in dev builds, since otherwise backtraces can take 20s+ to symbolize. With
# optimizations enabled, symbolizing a backtrace takes less than 1s.
addr2line = { opt-level = 3 }
adler = { opt-level = 3 }
backtrace = { opt-level = 3 }
gimli = { opt-level = 3 }
miniz_oxide = { opt-level = 3 }
object = { opt-level = 3 }
rustc-demangle = { opt-level = 3 }
[profile.release]
# Emit only the line info tables, not full debug info, in release builds, to
# substantially reduce the size of the debug info. Line info tables are enough
# to correctly symbolicate a backtrace, but do not produce an ideal interactive
# debugger experience. This seems to be the right tradeoff for release builds:
# it's unlikely we're going to get interactive access to a debugger in
# production installations, but we still want useful crash reports.
debug = 1